Steps to reproduce
We have two websites based on React js. They both fail with "This page is having a problem loading". I found a crash event log and related log files but there is little information that I can find to go on.
I’ve compiled attached archive with a static html page (sendsms, saved from Chrome) and the log files.
The site this page is from has been tested and works in Chrome, Firefox, IE11 and a range of mobile browsers.
I would appreciate if anyone could take a look at this bug and give me some pointers.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Christian F.”
Changed Assigned To from “Christian F.” to “Brad E.”
At the moment that is all I know, but will update once I have more details for you. I appreciate your patience while I look into this item of feedback.
All the best,
The MS Edge Team
We narrowed the issue down a shimmer css animation effect that we use for components while they load data from the backend. We are now investigating how we can tweak the shimmer effect to not trigger this error in MS Edge. The notLoaded css class is in the archive in msedge\sendsms_files\businesscare.css starting from line 538.
We found that the error is caused by a calc expression in a CSS animation keyframe. This bug is already logged here:
- Microsoft Edge Team
Changed Status to “Fixed”
Thanks for your patience on the matter.
I have now tested this repro you provided on a variety of different builds and will be attaching a screenshot of my results. The first Win 10 build number is highlighted with a box, the others are not highlighted but in the same place.
This does seem to have been fixed in later builds of Edge, I hosted the repro here for you to test:
You an also use the same later builds for testing by going here:
Hope this helps.
While this specific reason might be fixed, debugging sites when you just see the error is not at all fixed.
Since we’ll see this every time when something goes awry, we need to open tickets at MS instead of being able to look at the code that causes this.
Seriously, you need to implement a debug or inspect feature.
-> reason why edge gets ditched still.