You are probably affected by this closed bug .
There is no easy way to fix this right now, a fuzzy error message will probably not help (since you are not getting an HTTP error on the server side, this is only the browser that causes the error and truncates the connection).
On the other hand, the developer tool will not help either: Edge "smartly" automatically closes it when an error occurs, and if you open a story, it is empty (there is no way to save it, I tried all the buttons).
I have this problem on the site that I am developing, but I can’t understand what will happen.
EDIT - after a long time, I fixed this problem in my environment. Unfortunately, I am pretty sure that this will not help too many other developers, because the error seems to occur for a different reason, but still ... that is my usecase.
What froze my site was a combination of CSS media queries (follow the less used ones):
@media (min-width:calc(@screen-mobile-size + 1px)) { .hero_mobile { display: none; } .hero_desktop { display: inline; } }
... and a few lines below ...
@media (max-width: @screen-mobile-size) { height: auto; max-height: 600px; .hero_mobile { display: inline; } .hero_desktop { display: none; } }
I tested a lot of combinations, but there is only one rule: I can’t provide as media queries, no matter what is inside them! It just crashes the browser.
In my case, the fix was pretty simple: just prohibit embedding the first CSS rule inside the media query, so ...
.hero_mobile { display: none; } .hero_desktop { display: inline; } // ... @media (max-width: @screen-mobile-size) { height: auto; max-height: 600px; .hero_mobile { display: inline; } .hero_desktop { display: none; } }