It's more expected that you'll use things that use Houdini under the hood as an implementation detail.
A new layout mode (like CSS Grid) isn't available yet? This allows someone to write a polyfill for it. That's neat!
this was my first thought, too. We have polyfills for js features that don't yet exist in a lot of browsers, but polyfills for css are either very complicated or just don't exist in some cases.
Seems there is for parts of it already
Hopefully this won't be used as an excuse for new standards proposals to never move forward and/or browser teams to slow-roll implementing new standards natively..
UI is complex? Who knew!
It's 2021 and people still do div and javascript hell to implement these things.
There's even a color picker in native html now.
What about spinners, pull to refresh and other things ... would be nice to standardize all of these such that they display with your system's native widgets. The code for those CSS spinners is horrifying spaghetti code whereas I should be able to just do <spinner> and get an Android native spinner on Android and an iOS native spinner on iOS.
I think I get the point you're trying to make, and I find it difficult that someone could make a list of all the things that "should be in by default" vs providing the building blocks.
tl;dr they'll get it in the next patch
Web components is one way to add re-usable functionality naked into modern browsers. There is also a slew of new elements nobody seems to use for no good reason like: picture, figure, section, article, main, header, footer, the new input types, details and I’m sure I’m missing more.
Why does this industry think it’s okay to just be well educated with JS but doesn’t care that developers also know CSS and HTML just as well, I’ll never know
[0]https://lion-web.netlify.app/components/interaction/switch/o...
"npm i --save @lion/input-amount"
This isn't directed at you, but I shouldn't have to use npm to build a webpage. Also, building web components out of css/div hell severely impacts performance when you have a long scrollable list of them.
And most of these web components might look nice but they don't support native touch/swipe gestures in exactly the same way that the OS does.
I tried the Lion tabs component on my phone and I can't swipe between tabs. Probably the most utterly basic UI gesture. Fail.
And? That's what all the "native" web inputs are as well.
I wouldn't hold my breath though.
> Note: With great power comes great responsibility! With Houdini you could invent your own masonry, grid, or regions implementation, but doing so is not necessarily the best idea. The CSS Working group does a lot of work to ensure every feature is performant, handles all edge cases, and considers security, privacy, and accessibility.
Sounds like a lot of work to display a bloody list.