Conversation

Notices

1. Adrian Cochrane (alcinnz@floss.social)'s status on Saturday, 28-Jan-2023 04:46:29 JST Adrian Cochrane

   CSS is a fascinating language! Very straightforward to implement, even if a bit weird.

   After lexing there's no need for backtracking, since its very prefix-heavy. Occasionally infix for media queries or math().

   It degrades gracefully (unless you're targetting Dillo browser) so you shouldn't have to worry about whether browsers support any given feature.

   Interpreting it involves little more than a filtered & weighted deduplication. With most of the optimizing going into filtering.

   • Adrian Cochrane (alcinnz@floss.social)'s status on Saturday, 28-Jan-2023 04:53:15 JST Adrian Cochrane

     in reply to

     Design-wise CSS represents a design-negotiation between your device (represented by the useragent stylesheet), the reader, & the publisher. Though in fearing The Cascade (aforementioned weighting) & not showing an understanding of HTML, publishers are making it harder for the others to have their say.

     So please, learn CSS Cascade Layers (which are available in browsers now, including mine) & HTML!

   • Adrian Cochrane (alcinnz@floss.social)'s status on Saturday, 28-Jan-2023 05:19:09 JST Adrian Cochrane

     in reply to

     • Ekaitz Zárraga 👹

     @ekaitz_zarraga Here's MDN: https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Cascade_layers
     https://developer.mozilla.org/en-US/docs/Web/CSS/@layer

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Saturday, 28-Jan-2023 05:19:10 JST Ekaitz Zárraga 👹

     in reply to

     @alcinnz can you please link me to CSS Cascade Layers thingie? I didn't know it!

   • Adrian Cochrane (alcinnz@floss.social)'s status on Saturday, 28-Jan-2023 05:57:01 JST Adrian Cochrane

     in reply to

     • Ekaitz Zárraga 👹

     @ekaitz_zarraga

     at-import would've been easier if I wasn't implementing my engine in Haskell, but if you're going to remotely fetch multiple stylesheets anyways I've got no complaint... Just if you're worried about performance please don't nest CSS imports!

     P.S. You may want to combine at-import with Cascade Layers to avoid conflicts, there's syntax for that.

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Saturday, 28-Jan-2023 05:57:02 JST Ekaitz Zárraga 👹

     in reply to

     • Asia Link Import & Export

     @alcinnz Thank you! It looks very interesting!

     Also what's your feeling about @import? doesn't that slow down the loading of CSS files?

   • Adrian Cochrane (alcinnz@floss.social)'s status on Saturday, 28-Jan-2023 07:00:50 JST Adrian Cochrane

     in reply to

     • Ekaitz Zárraga 👹

     @ekaitz_zarraga To me this makes no difference, they both parse to the same thing in Haskell Stylist.

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Saturday, 28-Jan-2023 07:00:51 JST Ekaitz Zárraga 👹

     in reply to

     • Asia Link Import & Export

     @alcinnz thinking about performance, it should be better to include the styles in <link> tags instead of in the CSS imports, right? that way all of them would be downloaded right after the HTML file arrives (in parallel), while in the case of an \@import, the css that contains the import has to be downloaded first... that's one RTT more, isn't it?

     Why am I seeing this week many docs with the \@import added? is it a good practice even with that?

   • Adrian Cochrane (alcinnz@floss.social)'s status on Saturday, 28-Jan-2023 07:25:37 JST Adrian Cochrane

     in reply to

     • Ekaitz Zárraga 👹

     @ekaitz_zarraga If you at-import a stylesheet which at-imports additional ones, sure. Nothing the browser can do to optimize that, if you care about performance avoid it!

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Saturday, 28-Jan-2023 07:25:38 JST Ekaitz Zárraga 👹

     in reply to

     @alcinnz but regarding to network requests, the website will need more time to load, right?