Rezi
commented
4 months ago - I am also thinking about a navigation dropdown menu. Thanks for pointing out the article. It is pretty hard to do such a menu while be accessible and easy to change/extend.
- As for layers I am not sure whether to go with it or not. It is tempting as it can reduce the code. On the other hand it forces user to use layers. With :where() user just drop the css in and it works as it should. I'd love to hear more opinions on this before switching.
- With @use I can change that. There won't be any change in the compiled css. But it is probably good idea as @import could get deprecated in future in Sass.
This project seems good to me, since it is the only modern framework that uses only CSS and is very lightweight
And I was wondering if dropdowns would be added to this project? , they would be a good complement to the menus https://moderncss.dev/css-only-accessible-dropdown-navigation-menu/
On the other hand, wouldn't it be better to stop using where and have the user use layers? Layer support is almost the same as where, plus the code would be reduced a little more
layers 94.4% https://caniuse.com/css-cascade-layers
where 94.52% https://caniuse.com/mdn-css_selectors_where
And finally, I think that import @use should be used to make it compatible with other projects
Since it only occurs to me to import the sugar.css file before my sass project