cssweekly.com
Helping you stay up to date with CSS.
ðĨ YouTube: https://cssw.io/youtube
âïļ Mastering Linting: https://cssw.io/lint
ð·ïļ CSS Stickers https://cssw.io/stickers
347 posts
4,056 followers
475 following
Regular Contributor
Active Commenter
comment in response to
post
This seems cool, Arthur! Could you share the link? ð
comment in response to
post
This makes perfect sense. ðŊ
Do you usually work with Svelte and Vue? ð
comment in response to
post
Oh, that's very interesting! Thanks for sharing it! ð
Did you find any additional/specific drawbacks and challenges that pushed you to stop using them?
comment in response to
post
How come? ð
comment in response to
post
I created a guide on how to use them a while ago, in case you want to check it out: youtu.be/d6IbTQIL0uk
Am I reading this correctly, and your use cases are in WordPress? ð
comment in response to
post
That's fantastic, as always! Thanks for sharing it, Manuel! ð
Do you have any specific tricks, tips, or hacks for cascade layers? ð
comment in response to
post
Thanks so much for sharing this, Steve! It's a perfect fit for 3rd party plugins and widgets, but in reality, it's challenging to make it work. ð
Did you try with @import? And would a layer attribute for the <link> tag help with your use case?
comment in response to
post
Thanks for sharing this, Zell! ð
Do you have any specific examples? ð
comment in response to
post
This isn't ideal, but you can import them into a layer in CSS:
@import url layer(layer-name);
Also, there is a proposal to add a "layer" attribute for the <link> tag, but I don't think this has been implemented in any browsers yet. ð
comment in response to
post
Thanks for the heads-up, Matthew! ð
I tested it now, and it seems to be working (generally). Did you get any errors?
comment in response to
post
I'm not surprised at all, Adam. It was one of your CodePen demos that got me thinking about this again. ð
Having a @demo layer to single out the relevant code you want to showcase is so useful. ð
comment in response to
post
Oh, ok, gotcha! It makes sense, thanks for sharing it! ð
comment in response to
post
I'm really happy to hear this! Welcome aboard! ð
comment in response to
post
Oh, Sara, you could have guessed that the fun is in another window where I do things by hand. ð
Learning how to write better AI instructions is just a side quest. ðĪŠ
comment in response to
post
Ohhh, I got you then! ð
For some requests, it surprises me how well it can do; for others, like "change this button to blue," it updates the db schema and deletes 500 lines of random code. ðĪ·ââïļ
comment in response to
post
What's so funny? ð
comment in response to
post
Spot on, Billy. The irony is not lost on me. ð
Hopefully @hashnode.bsky.social will add this to their platform. ð
comment in response to
post
Frontend Focus newsletter: frontendfoc.us
comment in response to
post
Top 5 CSS Navigation Menu Mistakes: blog.css-weekly.com/top-5-css-na...
comment in response to
post
Oh wow, I never even considered that ReCAPTCHA might block real subs. I only considered it ineffective as a lot of spam still gets through. ð
I'll try replacing it with Turnstile to see if it makes a difference. ðĪ·ââïļ
comment in response to
post
Wow, 50%? Are those emails that end up on your list confirmed? ðģ
I added Google ReCAPTCHA a month ago to my landing page, and it helped a bit, but it's still ridiculous. I think many signups are stopped with a double opt-in, but I'll need to do an analysis soon and clean up my list again.
comment in response to
post
CSS Wizard is a 100% accurate title for you, Alvaro! ð§ââïļ
comment in response to
post
Yeah, this sounds about right! ð
comment in response to
post
Well, according to your infographics, some of us are wizards. ð
comment in response to
post
Thanks so much to @posthog.com for sponsoring! ð
To get hands-on tips on building better products, sign up for their fantastic newsletter: cssw.io/product-for-...
comment in response to
post
That's true, I've already seen it. ð
comment in response to
post
The attr() function in CSS got a lot better, and accepts type sice recently: attr(id type(<number>)); ð
Here is the explanation, in case you want to check it out: youtu.be/SfrhU6CLSo4
comment in response to
post
I"m so glad you think so, Sara! ðĪĐ
comment in response to
post
Oh dear, I only now noticed the "Nackgrounds" error. ð
comment in response to
post
I'm delighted to hear you think so! ð
comment in response to
post
Precisely, Caroline! ððð
comment in response to
post
The correct answer is: attr(id type(<number>)); ð
And here is the explanation: youtu.be/SfrhU6CLSo4
comment in response to
post
It happens in both cases when popped out and when anchored.
I initially thought it was something in this demo that was misbehaving, but it happens on every page in an iframe.