Wow..I was thinking about the concentric radius for some time. Really glad you guys have implemented it in ACSS. Kevin, Thank you so much for your time and effort in bringing this informative tutorial and for all the implementations. 👍👍
Great! My question is why would we keep the border framework enabled with a zero value instead of just disabling it and then enabling it in case we do happen to need the global borders later on?
I’m curious. Why did you choose to place your screen recording on a gradient background with padding, thus shrinking the viewing space and making it a little difficult to read? 🤔
I have to disagree about having the radius on by default. If I built dozens of sites with ACSS (which I have) before you added the feature, then when the plugin is updated, every one of them suddenly has an arbitrary radius applied to all my images. Now I have to go into all those sites and set the radius to zero. That seems like the antithesis of not being a chump.
Great lesson! Thank you. Is that possible to use a gradient border within the recipe? I remember you did something like that in the button lesson video.
@@AutomaticCSS Just design choice. Let's say i have an image in the top of a card for example, and i want only the top left and right corners to have a radius, how would i overwrite the bottom ones?
shouldn't the equation in the recipe be "border-radius: calc(var(--radius) + var(--padding) / 2 + var(--border-size))" instead of "border-radius: calc(var(--radius) + var(--padding) / 2 ?"
But this actually only works if each corner has the same radius value - because i only see one input field. So no separate t/r/b/l values possible or am i missing something?
I love the concentric radius feature! Thanks! 🙏🏻
Wow..I was thinking about the concentric radius for some time. Really glad you guys have implemented it in ACSS. Kevin, Thank you so much for your time and effort in bringing this informative tutorial and for all the implementations. 👍👍
Havent watched it yet but i already kno, gonna be FIRE 😎 happy new year to you and yours as well
Great! My question is why would we keep the border framework enabled with a zero value instead of just disabling it and then enabling it in case we do happen to need the global borders later on?
If you have border classes turned off, all it outputs is a few variables, one of which is the global radius variable which shouldn't be turned off.
@@AutomaticCSShm, i don’t really understand it but all in all it shouldn’t be turned off, okay
I’m curious. Why did you choose to place your screen recording on a gradient background with padding, thus shrinking the viewing space and making it a little difficult to read? 🤔
Because I knew it would get your attention
I have to disagree about having the radius on by default. If I built dozens of sites with ACSS (which I have) before you added the feature, then when the plugin is updated, every one of them suddenly has an arbitrary radius applied to all my images. Now I have to go into all those sites and set the radius to zero. That seems like the antithesis of not being a chump.
It’s not turned on by default on upgrades so this isn’t a problem.
@@AutomaticCSS That hasn't been my experience. I've literally had to go back to every website I built and turn it off
no, there was a bug when it was first released that turned it on but that was quickly fixed.
Great lesson! Thank you.
Is that possible to use a gradient border within the recipe? I remember you did something like that in the button lesson video.
No, because CSS doesn't accept gradients in the border field. We can look at adding compatibility for gradient borders, though.
@ would be a nice feature
In which frame rate did you record yourself? 🤔 The motion looks odd sometimes, and it’s not the lighting.
It’s a glitch in the software I was testing
how would i override the radius on an image with a figure tag while keeping auto radius on?
Depends on what purpose you're overwriting it for. What's the intention?
@@AutomaticCSS Just design choice. Let's say i have an image in the top of a card for example, and i want only the top left and right corners to have a radius, how would i overwrite the bottom ones?
@ border-radius: var(-radius) var(-radius) 0 0;
@@AutomaticCSS Thanks! that's what i've been doing but couldn't get it to work, i didn't realize the overflow. Just me being an idiot 😂
Thanks
shouldn't the equation in the recipe be "border-radius: calc(var(--radius) + var(--padding) / 2 + var(--border-size))" instead of "border-radius: calc(var(--radius) + var(--padding) / 2 ?"
Thanks Kevin!
if i understand this good, why can't we add variables to the border settings?
Not sure what you mean. Can you elaborate?
@@AutomaticCSS Why can't Acss have a variable class for the bricks border panel settings?
@@dovber There's no reason to.
But this actually only works if each corner has the same radius value - because i only see one input field. So no separate t/r/b/l values possible or am i missing something?
No you can have unique radius values but this is not required for most implementations
@@AutomaticCSS so i would have to setup my own radius class or define a var() right?
Damn! The new cinematic lighting with the Rembrandt triangle and all. Really popping!
🙏👍