March 8, 2019 at 4:58 PM #419667
Here are the credentials to the prototype. Once logged in, the “Ask for Time to Talk” course is the one you’ll launch. This course was published with the Web Accessible setting enabled, thus no seamless player. If time permits for a test, I’ll be curious to see if your Chrome browser is able to go full screen on the video page.March 8, 2019 at 5:22 PM #419669
Yes, by desktop I was meaning not a mobile device. Thanks for the html settingsMarch 8, 2019 at 5:27 PM #419671
Brian, I was able to reproduce the crash with your html options. I’ll follow with development on this and post back here with updatesMarch 8, 2019 at 9:24 PM #419679
As mentioned upthread, for reasons I don’t yet know it won’t maximize if, and only if, the course is AICC and launched from an LMS. Clicking the maximize button has no effect. (On Firefox I can right-click and go full-screen, but Chrome/Chromium does not allow this.) If I publish as HTML maximization works fine. No clue what’s up with that. I haven’t tested anything but AICC and HTML (no SCORM, no xAPI, etc.). I can’t test maximizing because … I can’t maximize.
Carl – Thanks my friend. You’ve given me some weekend reading!March 11, 2019 at 1:28 PM #419766
Brian, I opened a bug on the issue and we have development looking into this. Hoping to have something for our upcoming release. Thanks for the info to help me reproduce the errorMarch 11, 2019 at 2:44 PM #419781
Thanks man. I appreciate you guys scanning the forum and tackling these issues. If accepted as a bug and assigned a number, how might I track it?March 11, 2019 at 2:54 PM #419795
I can update this forum with any info, the intended release number, and the time frame of that release. Once the release comes out it will be in the release notes.March 11, 2019 at 4:27 PM #419806
Brian, you appear to be thinking of how open source projects track bugs. Lectora is very much proprietary software.March 12, 2019 at 3:42 PM #419997
Well, I just tried inserting a video into a course using the Lectora player today, and yes, it crashes on maximize in Chrome (only), but only when in AICC or SCORM format and launched from a server, not locally. If I publish to HTML and put the files on an IIS server I have access to, maximize does not cause the crash. What the?
Works fine in IE11, the only other browser I have here at work.
Edit: I went into the Chrome debugger and turned on breakpoints, then stepped through the entire process of maximizing one JS command at a time. It doesn’t crash when stepping through, naturally. Frustrating.
March 13, 2019 at 8:08 PM #420075
- This reply was modified 1 year, 6 months ago by CarlFink .
Darrel SomozaMember209 pts@Klaatu
Carl is the video you are adding a link to a file on another server or local?March 13, 2019 at 8:13 PM #420078
Can’t speak for Carl’s test, but I can say that I replicated the Chrome full screen crash using both a URL video link and a local video file.March 14, 2019 at 12:51 PM #420236
I only tried it with a local video. (Local to the HTML files–of course it was being served by a web server when launched from the LMS.)March 20, 2019 at 2:54 PM #420583
Today maximizing works normally. I suspect the a Chrome release fixed this bug. Of course when I went to check my version, Chrome updated again. Google is getting ridiculous with this stuff.March 20, 2019 at 3:09 PM #420586
Carl – Interesting result! I verified my baseline issue using my previous version of Chrome. Same blow up on video max. I then updated Chrome to what I assume is the very latest version <b>73.0.3683.86 (Official Build) (64-bit)</b> If I try to update again, it says Chrome is up to date.
Now, instead of an error, the maximized video just goes black. I can hear the audio of the video, but the screen is blank. I can hit Esc and return to windowed video just fine. I guess this is a step in the right direction, but still doesn’t have the full functionality I need.
You must be logged in to reply to this topic.