4 ms·
I have angered so many frontend devs by touting this for years. It amazes me how common sense like this is instantly attacked and belitteled. Unless you create
by trondeh80 3y ago
I have angered so many frontend devs by touting this for years.
It amazes me how common sense like this is instantly attacked and belitteled. Unless you create a user-interface UI in a webpage (a complicated frontend state), I think its way more reasonable to just use html/css with small sprinkles of js to open/close menues and modals. It loads fast, its less code so its easier to maintain. It does not require a complicated build step that instantly becomes deprecated once its deployed. Heck, its even greener, it requires less CPU power to build and render.
- rahkiin 3y agoI’ve found it is quite doable to have open/close menus purely with html and css these days using selectors! The text you click on is a label for a hidden checkbox. The checkbox you put adjacent to the item you’re hiding/showing. Then put css on it that uses input[type=checkbox]:checked and the tilde operator
- tonyedgecombe 3y agoI wonder why the HTML menu element was so half hearted. This is such a common requirement that it shouldn’t require hacks like that.
- qingcharles 3y agoAs CSS has developed over the last few years it is amazing how much you can now do on the front-end without JavaScript. I wish the browsers would enable their "behind-a-flag" support for masonry so many sites could then remove another chunk of JavaScript being used for layout.
- Zardoz84 3y agoactually you can do a pseudo masonry style using pure CSS with display: grid . I done it
- qingcharles 3y agoThere's a ton of things that sorta work, I use an all-CSS solution as a fallback for browsers that don't have the CSS property enabled. The problem is that all the pure CSS solutions order the grid in a different order than would be expected by the user. All the JavaScript solutions fix this, but, you know, JavaScript...