When the stock splits they don’t necessarily increase the number of your options, likely your number of stock options stays the same and the value goes down
@una any chance you could make an update on this? I saw that the spec was changed from @initial to @starting-style Would be great to also hear a discussion on when it makes sense to use this @ property and when other solutions make more sense. (also when considering vue-transitions or similar things provided by frameworks)
I don't get it though... like at what point does it go from display none to display block? At the start of the transition? end of the transition? middle? I'd love more info about how exactly this works.
Not helping, you should have description after that class (display- on-check), you already set the height of display-0n-check and then set opacity to 0, means no effect of display none, so no use of video
Thanks Maim your content is very student friendly. And your voice is so much crystal clear please make a playlist on Cascading style sheets from beginner level to Advanced web developer.🎉😊😊
Hey, very cool video! I just have a question seeing that this didn't work for me, but the situation is a bit different: I have a div with display:flex applied on it as soon as the DOM loads, and I would like it to gradually disappear and become a display:none as soon as you focus on a specific input field. Now, to do this I used your enumeration in the transition property and then changed those css values in-line with JS, but without the initial state (given that my div's initial state is a display:flex). Does it not work because of the lack of the initial block, or is it something else? Thanks in advance!
Love this! I had always wondered why browsers didn't support transition-delay & animation-delay for all properties... So cool to see this it being addressed now!
They do, but some properties aren't animatable. It hard to say what animation would make sense for properties like ‘display’. So, here is @initial property is added to make sensible approach. It's a draft, as far as I understand, so everything is subject to change.
Hi, i'm a brazilian React developer and just find yout channel now, I was looking for CSS layer content. I really liked the way you explain and started follow you. Thanks for the nice job!
Definitely quite awesome, but the entire @initial block seems like something the browser should be able to figure out for me, without me having to duplicate the CSS that I have already applied to the element... 😕
Then it would be a bit more of an abrupt disappearance and opacity wouldn't finish going to 0 (you can try it out yourself in Canary behind the experimental web platform features flag)
Best place for now is CSSWG issues: www.google.com/url?sa=j&url=https%3A%2F%2Fgithub.com%2Fw3c%2Fcsswg-drafts%2Fissues%2F8174&uct=1657644384&usg=J9N7WUnmKRr8QKG7GTJYZWin3as.&source=chat
The clearest explanation that I found about CSS layers. I would love to hear your thoughts about how you think this tool can affect the overarching topic of CSS architecture :)
thanks. So how is having color: revert-layer different then not having it there at all? will it not show whatever is resolved up to the pervious layer anyway?
Thank you, interesting... Certainly the opposite of what I expected along the lines of common sense. I wonder what's the benefit of doing it this way, for ex. when would an !important user-agent style be more important than the author's !important wish?
OMG I wrongly assumed user stylesheets always had the highest specificity. Because how else could a user apply preferred link colours? But the answer actually is !important, it seems! When picking “Always set these colours“ in Firefox, this is probably adding an !important to the user styles, which in turn will even overrule !important rules in the author stylesheet. On the other hand, user stylesheets without !important are probably pretty useless.
