Thanks for the video Jeroen. You're a CSS Magician that lives in the bleeding edge. I saw that If we put the buttons to the bottom right (makes more sense for mobile to me) then there's an overflow problem. If the content of the menu creates an scroll bar, the close button keeps moving with the scroll position. This can be solved by making the close button fixed rather than absolute. And there's no need to play with the overflow properties as is.
Thanks for this video could you make a video on CSS trig functions I've seen ana tudor doing great things on codepen like her " No SVG, no image, CSS-only fluid slider with input"
The specs make a distinction which they call “modal” or”non-modal”. A dialog is a modal pop-up, which means that in order to dismiss that, the user _has_ to make an important choice in the dialog before it can be dismissed. The popover is non-dialog, meaning it does not have that restriction. This is also why for example the popover auto closes when you click the backdrop vs a dialog which you need to run a JS method for this to happen. There’s a lot of overlap between the two elements and you can definitely create a non modal with a dialog too. But this is what the docs say is their intended behavior. See here too: developer.mozilla.org/en-US/docs/Web/API/Popover_API#concepts_and_usage
In dit geval combineer je het met bijv opacity 0 om een fade-in te krijgen. Display none en block hebben zelf geen waardes waartussen ze geanimeerd kunnen worden. Dus als je animeert naar display none, zal de browser op het laatste moment de property naar none zetten. Om dan een animatie te zien moet je zelf nog opacity animeren.
@starting-style is a game changer wooo thanks for making a vid on this
Thanks for commenting! Glad you liked the video!
Thanks for the video Jeroen. You're a CSS Magician that lives in the bleeding edge. I saw that If we put the buttons to the bottom right (makes more sense for mobile to me) then there's an overflow problem. If the content of the menu creates an scroll bar, the close button keeps moving with the scroll position. This can be solved by making the close button fixed rather than absolute. And there's no need to play with the overflow properties as is.
bro something lol i found when u write this : popover=" " i didnt an :
///
but i use it anyways cause i can make some error
Thanks for this video
could you make a video on CSS trig functions
I've seen ana tudor doing great things on codepen like her " No SVG, no image, CSS-only fluid slider with input"
It's such a simple but awesome feature. It's always such a pain to implement this in jsx especially if you want animations
I really like it! And that fact that is so new but we can use it everywhere already is even more amazing. I love the direction CSS is heading into!
bro bro make a video about :has() :is() and so on. come on bro u re the best
What vscode theme are you using? I like the font also. I would like to change mine :)
It's called Arc, from the Bearded Theme collection: github.com/BeardedBear/bearded-theme
The font is called Recursive Mono Casual Static
@@frontendfyi thank you 😊💃
What VSCode theme are you using, Jeroen?
It's called Arc, from the Bearded Theme collection: github.com/BeardedBear/bearded-theme
The font is called Recursive Mono Casual Static
Is there a difference from the dialog element, other than being pure css.
The specs make a distinction which they call “modal” or”non-modal”. A dialog is a modal pop-up, which means that in order to dismiss that, the user _has_ to make an important choice in the dialog before it can be dismissed.
The popover is non-dialog, meaning it does not have that restriction. This is also why for example the popover auto closes when you click the backdrop vs a dialog which you need to run a JS method for this to happen.
There’s a lot of overlap between the two elements and you can definitely create a non modal with a dialog too. But this is what the docs say is their intended behavior.
See here too: developer.mozilla.org/en-US/docs/Web/API/Popover_API#concepts_and_usage
This is so great I've been looking for a developer RUclipsr who also teaches accessibility
Nice!! Happy you like my content 🙏 Always feel free to share ideas for topic you’d like to see content of.
What theme are you using for vs code?
It's called Arc, from the Bearded Theme collection: github.com/BeardedBear/bearded-theme
The font is called Recursive Mono Casual Static
Can somebody name his font????????
The font is called Recursive Mono Casual Static
Nice!
10/10
So kind!! Thanks 🙏
What a great video!
Thank you!!
I'm excited
🔥🔥
Eventually we will get rid of all these UI libraries. Hopefully. Thanks for the great content😊
I love the direction css is heading into. Doing these things with plain css definitely is the way! Glad you like the content 😌
Which theme?
It's called Arc, from the Bearded Theme collection: github.com/BeardedBear/bearded-theme
The font is called Recursive Mono Casual Static
Ahhhh yesss, eindelijk transitions van display:none naar flex! Neem aan dat dit altijd gebruikt moet worden i.p.v. opacity:0; visibility:hidden toch?
In dit geval combineer je het met bijv opacity 0 om een fade-in te krijgen. Display none en block hebben zelf geen waardes waartussen ze geanimeerd kunnen worden. Dus als je animeert naar display none, zal de browser op het laatste moment de property naar none zetten. Om dan een animatie te zien moet je zelf nog opacity animeren.
I ❤ this channel … thank you so much for sharing and teaching us ✌️
Glad you enjoy it! Thanks for sharing this with me too! ❤️
Liked and subscribed!!!
Thank you! 🙏
this is just amazing
thanks bro
Glad you liked it!