Oh man please remove this and replace it with a normal <link rel=stylesheet ...> to avoid that nasty FOUC on first load:
```
<link href="https://www.aaron-gustafson.com/c/advanced.min.css" rel="preload" as="style" onload='this.onload=null,this.rel="stylesheet"'>
```
```
<link href="https://www.aaron-gustafson.com/c/advanced.min.css" rel="preload" as="style" onload='this.onload=null,this.rel="stylesheet"'>
```
December 10, 2025 at 7:51 PM
Oh man please remove this and replace it with a normal <link rel=stylesheet ...> to avoid that nasty FOUC on first load:
```
<link href="https://www.aaron-gustafson.com/c/advanced.min.css" rel="preload" as="style" onload='this.onload=null,this.rel="stylesheet"'>
```
```
<link href="https://www.aaron-gustafson.com/c/advanced.min.css" rel="preload" as="style" onload='this.onload=null,this.rel="stylesheet"'>
```
I have done so much work on my blog the past few days. Three posts in two days.
None of them good, but hey, it's out there. And the FOUC bug is fixed!
None of them good, but hey, it's out there. And the FOUC bug is fixed!
December 9, 2025 at 5:56 PM
I have done so much work on my blog the past few days. Three posts in two days.
None of them good, but hey, it's out there. And the FOUC bug is fixed!
None of them good, but hey, it's out there. And the FOUC bug is fixed!
just not at all obvious what the benefit is supposed to be. requires a bunch of extra client-side logic, results in FOUC if SSRing, and (at least with current devtools) you can't inspect the ranges. if you could set ranges with CSS it would be useful, but as it is... just seems pointless tbh
December 2, 2025 at 6:23 PM
just not at all obvious what the benefit is supposed to be. requires a bunch of extra client-side logic, results in FOUC if SSRing, and (at least with current devtools) you can't inspect the ranges. if you could set ranges with CSS it would be useful, but as it is... just seems pointless tbh
Seems like it does the job, but I personally feel like it’s a bit overkill to read UI preferences on the server just to avoid a FOUC (or whatever we call it now), a blocking script or client side Suspense boundary seems like a better for IMO
December 1, 2025 at 12:08 PM
Seems like it does the job, but I personally feel like it’s a bit overkill to read UI preferences on the server just to avoid a FOUC (or whatever we call it now), a blocking script or client side Suspense boundary seems like a better for IMO
the hoodie on this would have been incredibly difficult without it bsky.app/profile/fouc...
November 27, 2025 at 12:42 AM
the hoodie on this would have been incredibly difficult without it bsky.app/profile/fouc...
SolidStart を導入してるんですけど、 FOUC (Flash of Unstyled Content) がまあまあ気になりますね...
November 24, 2025 at 11:19 AM
SolidStart を導入してるんですけど、 FOUC (Flash of Unstyled Content) がまあまあ気になりますね...
Fouc off!
a black and white photo of a bald man wearing glasses and a turtleneck
ALT: a black and white photo of a bald man wearing glasses and a turtleneck
media.tenor.com
November 20, 2025 at 7:32 PM
Fouc off!
Alison Bechdel a produit de nombreux comics qui ne sont plus édités, et ces deux cases qu'elle a présentés lors d'une conférence à Yale me donnent très envie d'en lire plus : bsky.app/profile/fouc...
Lors de la conférence, elle a présenté ces deux cases tirées d'une BD intitulée Lesbophobias, sur les peurs spécifiques aux lesbiennes. J'adorerais lire le reste !
November 16, 2025 at 5:06 PM
Alison Bechdel a produit de nombreux comics qui ne sont plus édités, et ces deux cases qu'elle a présentés lors d'une conférence à Yale me donnent très envie d'en lire plus : bsky.app/profile/fouc...
November 14, 2025 at 8:38 PM
Bye bye FOUC, hello smooth animations.
Webflow just launched an update creators were waiting for: automatic handling of Flash of Unstyled Content (FOUC) in GSAP interactions.
That brief moment when an element appeared unstyled before your animation started? Gone.
A small update, but a big boost.
Webflow just launched an update creators were waiting for: automatic handling of Flash of Unstyled Content (FOUC) in GSAP interactions.
That brief moment when an element appeared unstyled before your animation started? Gone.
A small update, but a big boost.
November 12, 2025 at 9:15 AM
Bye bye FOUC, hello smooth animations.
Webflow just launched an update creators were waiting for: automatic handling of Flash of Unstyled Content (FOUC) in GSAP interactions.
That brief moment when an element appeared unstyled before your animation started? Gone.
A small update, but a big boost.
Webflow just launched an update creators were waiting for: automatic handling of Flash of Unstyled Content (FOUC) in GSAP interactions.
That brief moment when an element appeared unstyled before your animation started? Gone.
A small update, but a big boost.
Moose . AI
Eh . I
Doubledouble
Timbyts
Eh . I
Doubledouble
Timbyts
November 11, 2025 at 6:30 AM
I've addressed a lot of the feedback received on this, thank you all so much for taking a look.
I still have a FOUC on load but I plan to address that when I make my for-realsies theme switcher. For now I'm focusing on getting the theme itself right.
I still have a FOUC on load but I plan to address that when I make my for-realsies theme switcher. For now I'm focusing on getting the theme itself right.
Alright, so for the last couple weeks I've been working on dark mode for samwho.dev. It has been really hard work. This is my first time designing a dark mode theme, and I didn't make it easy on myself, so I am very humbly asking for your feedback 🙏
samwho.dev/big-o?theme=...
samwho.dev/big-o?theme=...
Big O
A visual introduction to big O notation.
samwho.dev
November 10, 2025 at 10:23 PM
I've addressed a lot of the feedback received on this, thank you all so much for taking a look.
I still have a FOUC on load but I plan to address that when I make my for-realsies theme switcher. For now I'm focusing on getting the theme itself right.
I still have a FOUC on load but I plan to address that when I make my for-realsies theme switcher. For now I'm focusing on getting the theme itself right.
Sounds good, I'm curious what's the issue with it, or what demonstrates?
pd: FOUC is Flash of unstyled content, not "Frame". I suppose a Flash could happen within many frames. 🤓
pd: FOUC is Flash of unstyled content, not "Frame". I suppose a Flash could happen within many frames. 🤓
November 10, 2025 at 12:38 PM
Sounds good, I'm curious what's the issue with it, or what demonstrates?
pd: FOUC is Flash of unstyled content, not "Frame". I suppose a Flash could happen within many frames. 🤓
pd: FOUC is Flash of unstyled content, not "Frame". I suppose a Flash could happen within many frames. 🤓
Okay how about FOEC: frame of early-styled content.
FOUC and FOEC, I kinda like this.
FOUC and FOEC, I kinda like this.
November 9, 2025 at 2:56 PM
Okay how about FOEC: frame of early-styled content.
FOUC and FOEC, I kinda like this.
FOUC and FOEC, I kinda like this.
FOUC is what my wife sees when I get out of the shower
November 9, 2025 at 8:01 AM
FOUC is what my wife sees when I get out of the shower
Lets say you have two routes, route A sets the background-color of body to red, route B sets it to green.
Now when you clientside navigate from A to B, you wanna load the styles of B early to avoid FOUC, but you only wanna show the green background once B is ready for rendering.
Now when you clientside navigate from A to B, you wanna load the styles of B early to avoid FOUC, but you only wanna show the green background once B is ready for rendering.
November 8, 2025 at 6:20 AM
Lets say you have two routes, route A sets the background-color of body to red, route B sets it to green.
Now when you clientside navigate from A to B, you wanna load the styles of B early to avoid FOUC, but you only wanna show the green background once B is ready for rendering.
Now when you clientside navigate from A to B, you wanna load the styles of B early to avoid FOUC, but you only wanna show the green background once B is ready for rendering.
you think FOUC is the worst only until you meet FOTESC
November 7, 2025 at 10:52 PM
you think FOUC is the worst only until you meet FOTESC
Not sure if I follow. Even if you load them in the head you still have to do customElements.define and that delays your component's display content. Pretty sure one needs proper fallback content to avoid LS and FOUC, regardless of where the components are loaded.
November 7, 2025 at 12:19 PM
Not sure if I follow. Even if you load them in the head you still have to do customElements.define and that delays your component's display content. Pretty sure one needs proper fallback content to avoid LS and FOUC, regardless of where the components are loaded.
If you let your web components define too much of the actual content, you get things like layout shifts and FOUC. Those suck, you don't want those. In this pug template you can see how things get slotted into the web components (the tags beginning with alfred-*). All the page structure is here.
November 7, 2025 at 4:01 AM
If you let your web components define too much of the actual content, you get things like layout shifts and FOUC. Those suck, you don't want those. In this pug template you can see how things get slotted into the web components (the tags beginning with alfred-*). All the page structure is here.
1. Here’s how I avoid a FOUC on my own website: github.com/mxdvl/mxdvl/...
2. See attached video on the right side — maybe a stroke-dasharray / -dashoffset issue?
2. See attached video on the right side — maybe a stroke-dasharray / -dashoffset issue?
November 5, 2025 at 11:31 PM
1. Here’s how I avoid a FOUC on my own website: github.com/mxdvl/mxdvl/...
2. See attached video on the right side — maybe a stroke-dasharray / -dashoffset issue?
2. See attached video on the right side — maybe a stroke-dasharray / -dashoffset issue?
me fixing some FOUC issues on my site
November 5, 2025 at 2:14 PM
me fixing some FOUC issues on my site
To avoid FOUC, we have all of the elements set to visibility: hidden in the global document, then the shadow DOM stylesheet will override that and make them visible.
For any elements CSR'd after page load, we use that same stylesheet as a CSSStylesheet (or <style> if browser doesn't support)
For any elements CSR'd after page load, we use that same stylesheet as a CSSStylesheet (or <style> if browser doesn't support)
November 5, 2025 at 12:00 AM
To avoid FOUC, we have all of the elements set to visibility: hidden in the global document, then the shadow DOM stylesheet will override that and make them visible.
For any elements CSR'd after page load, we use that same stylesheet as a CSSStylesheet (or <style> if browser doesn't support)
For any elements CSR'd after page load, we use that same stylesheet as a CSSStylesheet (or <style> if browser doesn't support)