4 ms·
I'd ask what you mean by "fighting the browser"- as generally, the number one way to ruin the performance of your CSS is to introduce depth to it. In general, k
by quaunaut 2y ago
I'd ask what you mean by "fighting the browser"- as generally, the number one way to ruin the performance of your CSS is to introduce depth to it. In general, keeping everything isolated regularly leads to better rendering performance.
- no_wizard 2y agoAvoiding the cascade at all costs, for example. It can introduce a lot of unintended consequences. Another anti pattern I have seen is the over use of media queries to force the browser to do certain things rather than embracing relative sizing constraints via intrinsic design and letting the flexbox and grid algorithms do most of the heavy lifting. Here though I want to point out isolation is relative, as is the cascade. I think it’s important to leverage the cascade wherever you can but that doesn’t mean you are leveraging it from top to bottom per say, but it does mean thinking more wholistic about the context of styling
- ThunderSizzle 2y agoTo be fair, there was a time that flexion did not exist and extensive use of media queries was the only way to create a responsive website. Those efforts don't just dissappear quickly, since that was the only way available that worked across all browsers for nearly a decade.
- skydhash 2y agoIsn’t the browser responsive by default? The only issue I see is taking a layout built for refloyable documents and wanting to create applications and magazine-like design with it. Now it’s possible but it’s always more convulated than something like the tools available on platforms like iOS and Android.