Forum Discussion
New Release- Lightbox error?
Hi! Just updated to the latest release, and my lightbox slides have gone wonky. How do I fix this? Is it a new bug?
If my browser is full screen the lightbox is too large and cropped and the x is not accessible. If my browser is smaller the lightbox is too small. (The player settings allow to resize to fill screen.)
I've attached images. My project is due Monday!?!?!
It might not suit everybody, but my workaround is to just create my own 'Close' button on lightbox slides using the 'Close lightbox' trigger. It doesn't resolve any sizing issues but gets me through my review process.
Hi, it would be really helpful to have an update to know in what timescale the lightbox bugs reported here are being resolved thanks.
Our team is currently working on this and we hope to have a fix out to you soon.
By replying here, you should be subscribed so that you get updates to this forum thread and we will post an update.
Hi all,
The issue with Lightbox slides covered the entire course when the player was set to fill the browser in HTML5 output was fixed in the Articulate 360 update released today!
Take a look at the release notes here, and you can install the latest update from the Articulate 360 desktop tray application by clicking Update.
Hi Traci
try creating a new project file and importing your slides in to see if that helps. Also check your player/browser settings haven't changed.
Hi Wendy! Thanks for the quick response. I'm working on a 6-month long project that is due on Monday. There are so many variables and triggers to make it work. Rebuilding or importing the module isn't an option this late in the game.
I was able to replicate the issue in a new module. I've put in a ticket. Hopefully there is a workaround or solution. 01273396
Just to add from my testing, this is an issue if the browser is allowed to fill the screen. If it's locked then it doesn't seem to be a problem. I did a new test item, and I can't even see the x to close the lightbox. Also the too large/cropped version of the lightbox seems to happen in Chorme not IE.
I'm seeing the same thing, Traci. It doesn't occur in the Flash output, only HTML5.
Same behaviour experienced.
In the ticket response they have logged it as a “possible bug.” And suggested locking the player as a workaround.
Hmm. If a new release, which includes a "fix" related to the lightbox, (Fixed: We fixed some issues with lightboxes in HTML5 output, including matching questions that wouldn't work and exit buttons that were offscreen) results directly in said feature no longer behaving as it very recently did, one would hope the word "possible" disappears quickly from the log.
Anyway, regarding the workaround, does "locking the player" refer to player/other/player size/lock player at optimal size?
I think you're correct on the lock player to optimal size as the setting. It seems to fix the issue. This isn't an option for me, so I think I will restructure a bit so that lightbox slides become layers or just regular slides. Not ideal, but I don't think it will be solved right away. On the bright side the CC on the Lightbox slides is working now.
I am having the same issue (as explained here: https://community.articulate.com/discussions/articulate-storyline/since-the-latest-update-lightbox-slide-larger-than-course-player#reply-499108 )
The issue with locking the player at optimal size is that it doesn't scale to fit the screen sizes of different devices. So for example, if someone has a small screen on their pc, there is potential that they will need to scroll around the screen to see the content.
Can anyone from the Articulate team comment on this?
Hi John,
I understand that this is not ideal, but it was the recommended workaround in the meantime, and we are working on the reported issue.
I apologize for the inconvenience and we will be sure to update you here when we can.
Hi Leslie
Thank you for your reply. Do you know what the time frame for this fix would be? I am working on a large project that consists of 64 Storyline project files and need to get this fixed as soon as possible.
Many thanks again.
