[FIREFOX] Website broken?

[Chalarangelo]

@atomiks @fejes713 @skatcat31 @flxwu Website seems to be broken for me. We need to address this asap!

Notes

• This only seems to happen on Firefox on my PC, works properly for Chrome.
• No errors in console.

[Chalarangelo]

This is what I see on Firefox on my PC and after a few seconds it goes blank.

[AlejandroMataGuillen]

@Chalarangelo Just tested on Firefox 61.0.1 (Ubuntu 17.10) and works well

[fejes713]

OS: MacOS

• Just tested on Firefox Developer Edition version 62 and works just fine.
• Tested on Chrome as well, works fine. - Linting for code is sometimes broken (semicolons go to start of the next line).

Thanks @AlejandroMataGuillen for testing 👍

[fejes713]

Please report if you experience such issues on other systems / browsers. This is major issue if its consistent.

[atomiks]

Not seeing any problems on Firefox either (61 & 62), but that's Mac not PC

[Chalarangelo]

Can't reproduce on a similar setup (Win 10, Firefox). It's probably a problem with my home PC, so I'll check back in the afternoon, figure out the reason why.

[flxwu]

Works for me on Firefox (62) & Chrome (v. 71) aswell

[fejes713]

Thanks for testing it out @flxwu @atomiks 👍 Hopefully its just problem with @Chalarangelo PC.

I am closing this for now. If some of you run into the same issue again, feel free to reopen this as its a huge issue.

[skatcat31]

FF is known to be a browser currently undergoing some pains. It's having issues parsing large JSON(above a few KB, has been since the rework), some CSS3 logic(some real edge cases here about composition of transformations triggering other transformations), and a bad parser for date times that sometimes does not resolve the TZ(seems to be fixed as of 61 at least).

This issue however would be a parsing of inline scripts, which would be a serious problem that would have been reported as "OMGZ FireFox is broke, E'ERYONE CLICKBAIT" or something on Gizmodo and The Verge, so I'm guessing it's local.

Tested and working just fine on FF 61/62, Chrome/Canary, and M$ Edge. IF you can constantly recreate this we'd love to see a version number. Their issue tracker may have more information if we can get that

(also sorry for absence, had an event, then getting ready for reception... gonna be a busy AF month)

[fejes713]

Hey @skatcat31 Thanks for detailed report, I appreciate it very much. We should be stable now, should I close this issue or leave it here if someone encounters the same behavior?

[skatcat31]

I think it's safe to close as a "unrepeatable local problem"

[fejes713]

Closing this after receiving feedback from a few more people. Feel free to reopen if you encounter the same problem again.