4 ms·
To me, I think this is where HTML standards went off the rails. Rather than working on, say, the vibration API, give us built in web components that are stylab
by another-dave 2y ago
To me, I think this is where HTML standards went off the rails.
Rather than working on, say, the vibration API, give us built in web components that are stylable but also accessible by default.
In 2024, half of the things in Bootstrap or Tailwind UI should be obsolete. Where's our OOTB carousel, date picker, rich drop-down with icon/subtext, form elements supporting AJAX state, modal windows? etc etc.
All of these things should be as foolproof as an unordered list for devs to implement & the quality of websites in terms of performance & accessibility would be lifted massively
- robertoandred 2y agoWe’ve had date pickers and modals, and scroll snapping gets you halfway to carousels.
- mcaruso 2y ago> Where's our OOTB carousel, date picker, rich drop-down with icon/subtext, form elements supporting AJAX state, modal windows? etc etc. You might want to take a look at what browsers have been working on lately, because a lot of what you're asking is either already here or actively developed. Some of it driven by the Open UI working group (https://open-ui.org https://open-ui.org). - Modal: see the <dialog> element, with its focus trapping out of the box, stylability through the top layer, entry and exit animations through @starting-style and the ability to transition discrete properties like `display`, etc. - Rich dropdown: browsers now support popovers, which allow you (without any JS) trigger a popover that overlays the screen in the top layer, and with automatic focus management. See also the work being done on stylable <select> elements, there's a great episode of Off The Main Thread that goes deep into all the work being done to make this happen [1]. - Carousel: see the recent work on stylable <details> elements [2], and in general the carousel project at Open UI. After <select>, the carousel is one of the main focus areas. [1] https://offthemainthread.tech/episode/stylable-select-element/ https://offthemainthread.tech/episode/stylable-select-elemen... [2] https://chromestatus.com/feature/5112013093339136 https://chromestatus.com/feature/5112013093339136 [3] https://open-ui.org/components/carousel.research https://open-ui.org/components/carousel.research
- cluckindan 2y agoHere: <input type=”date”>
- another-dave 2y agoExactly my point — compare the feature set of this, vs the experience you'd expect from an airline or hotel booking site. Stuff like entering a date range or showing additional info inline is impossible (colour-coded availability or price details, say). Then you get onto `type="datetime-local"` and there's just no input for times at all apart from typing manually in the input field. Google make the browser & even they don't use `input type="date"` on Google Calender — the gap is too far between the desired look & feel/functionality vs what's possible so people end up reimplementing it, which is a complete waste of everyone's efforts.