3 ms·

What's with the blip/FOUC?

• beeskneecaps 9y ago
  35ms faster FOUCs!
• irrational 9y ago
  Yeah, that's super annoying. I would think that a team that can build react could build a site with it that doesn't have FOUC. If they can't do it, what hope do the rest of us have?
• toufka 9y ago
  And the page doesn't even come back from the flash in my semi-locked down firefox. It flashes content, then back to a white page without an empty <body>: DOMException [SecurityError:"The operation is insecure." Code 18: location: https://reactjs.org/commons-f40206259909ee9b7a40.js:4]`
  • danabramov 9y ago
    Can you please file an issue and describe more about your FF configuration?
• tarr11 9y ago
  Looks like it's related to their use of TypeKit for fonts. I haven't used TypeKit in a while, but it looks like they had this issue a year ago [1]. Unclear if it has been fixed or what. A lot of people I know simply embed the font in the page (ugh) [1] https://blog.typekit.com/2016/06/03/regarding-the-flash-of-unstyled-text-in-chrome-50/ https://blog.typekit.com/2016/06/03/regarding-the-flash-of-u...
  • danabramov 9y ago
    We're looking into it, sorry about that.
• triptych 9y ago
  I notice that right away. Reloading over and over you can see it very clearly.