I'm running into an issue where, depending on the computer (although I don't know what is different about them), certain lesson pages are not loading when I Preview them or view the Shared version (in Chrome). When I click to go to the lesson, the header appears for the lesson, but none of the content appears below it, although it acts as if it is invisible, because I can scroll down the page, and the cursor changes where there would presumably be images, but it is all just a sea of white.
I've noticed that these pages have 7 or 8 blocks on them, some with large images. Could this be causing the page not to load?
Thanks Will for reaching out here - it's not something I've seen yet, but I'd want to follow along with your Support case (# 01010771 for my reference) that you're working on with Gren right now. I see she's doing some testing - so we'll keep you posted!
It looks like Gren reached out with steps to share your Rise course with her so that we could take a look at the behavior you described. If you're able to send it along using the directions she shared - please do so and I'll continue to follow along in your case.
I just checked in on your course, and I see that Gren asked for a copy of your zipped course export. If you're able to upload that and share with her she'll be able to keep looking into the issue you shared here.
It looks like Will and Gren are still troubleshooting his issue with the particular Rise course - I'll keep an eye on the case so that I can update you all here.
So I determined that the cause of this was that some users were on version 41 or 42 of Chrome (the most current version of Chrome is 56). If Chrome is too old, unfortunately what the user sees is content that just doesn't display correctly. Which makes me wish there was something that notified the user they were using an outdated browser (ala the way gmail does).
Thanks Will for the update - I had a note to check in on your case with Gren today! I also see you've got some other discussions about browser support - so we'll take a look at the information and respond there!
Thanks Ashley. Unfortunately I guess we've moved past the day when you could assume Chrome rendered HTML5 the same regardless of version. Maybe that day was a long time ago and I just wasn't aware until now.
If you're interested, you can scroll down to the line graph on this page and see how various browsers continue to grow in maturity. It looks like Chrome 40 achieves a score of 456 (out of 555), whereas Chrome 56 is up to 519!
13 Replies
Thanks Will for reaching out here - it's not something I've seen yet, but I'd want to follow along with your Support case (# 01010771 for my reference) that you're working on with Gren right now. I see she's doing some testing - so we'll keep you posted!
Hi Will,
It looks like Gren reached out with steps to share your Rise course with her so that we could take a look at the behavior you described. If you're able to send it along using the directions she shared - please do so and I'll continue to follow along in your case.
Hi Will,
I just checked in on your course, and I see that Gren asked for a copy of your zipped course export. If you're able to upload that and share with her she'll be able to keep looking into the issue you shared here.
Sorry for the delay. I will get this uploaded. Too many projects at one time. :-)
Hey Will! How's life treating you these days?
Forgot to mention... I'm interested in Will's question as well...
It looks like Will and Gren are still troubleshooting his issue with the particular Rise course - I'll keep an eye on the case so that I can update you all here.
So I determined that the cause of this was that some users were on version 41 or 42 of Chrome (the most current version of Chrome is 56). If Chrome is too old, unfortunately what the user sees is content that just doesn't display correctly. Which makes me wish there was something that notified the user they were using an outdated browser (ala the way gmail does).
This post was removed by the author
You can see what the latest version is here: https://en.wikipedia.org/wiki/Google_Chrome_version_history
The reason they were still on version 41 was that in version 42:
Support for NPAPI plugins disabled by default
Thanks Will for the update - I had a note to check in on your case with Gren today! I also see you've got some other discussions about browser support - so we'll take a look at the information and respond there!
Thanks Ashley. Unfortunately I guess we've moved past the day when you could assume Chrome rendered HTML5 the same regardless of version. Maybe that day was a long time ago and I just wasn't aware until now.
Hey, Will.
If you can believe it, browser support for HTML5 is still actively evolving, and I think that's expected given that the specification was finalized just over 2 years ago. 😀
If you're interested, you can scroll down to the line graph on this page and see how various browsers continue to grow in maturity. It looks like Chrome 40 achieves a score of 456 (out of 555), whereas Chrome 56 is up to 519!
This discussion is closed. You can start a new discussion or contact Articulate Support.