- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Aug 2020 02:35:29 +0000
- To: public-css-archive@w3.org
Ok, had a little bit of time to sit down and update the Slider analysis on Open UI. The concepts across libs can be seen [here](https://open-ui.org/components/slider.research). But more importantly, I dug into each for the part concepts they support and the subsequent naming of these sub-parts. The table rendered below can be seen [here](https://open-ui.org/components/slider.research.parts). <img width="1349" alt="Screen Shot 2020-08-25 at 7 28 27 PM" src="https://user-images.githubusercontent.com/865244/91248287-2f269100-e709-11ea-866a-e0c666cade59.png"> <img width="1327" alt="Screen Shot 2020-08-25 at 7 29 01 PM" src="https://user-images.githubusercontent.com/865244/91248327-44032480-e709-11ea-890c-b6254a4b2fa2.png"> Based on this, specific to your proposal I am `thumb` and `track` win out across almost all endpoints. `progress` not so much but there isn't much agreement here across the industry it seems but there is agreement that this is needed, even though a few don't currently ship with this supported. A few that I'll propose for the Open UI anatomy will be number output, content start/end, marks, steps, mark content and probably tooltip. So basically for now I'll avoid two handles. That said nothing in the above will block this. We may want to consider marks, steps and mark content as these are actually already standardized - some UAs render them and others don't but they aren't reachable. To scope to this I think I'll just give my support to the current proposal and create a new one for those others to bring interop on the prefixed ones. -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4410#issuecomment-680424639 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 August 2020 02:35:31 UTC