06:50
<annevk>
CSS module scripts are standardized in HTML, not in CSS. The idea is that you can append whatever you imported to a style sheet set. For instance, a style sheet set belonging to a shadow root.
07:45
<hsivonen>
Ambiguous ampersand made it to Nightly. 🎉 Thanks sideshowbarker !
08:14
<sideshowbarker>
Ambiguous ampersand made it to Nightly. 🎉 Thanks sideshowbarker !
Excellent — laissez les bons temps rouler
10:17
<stephanluis>
annevk: Ok. already back with the first example of where javascript is not sufficient for modifying the time input into a duration input. The hurdle is that Safari adds AM or PM and converts to a 12hr clock. While the 12hr conversion is straightforward to deal with -- for a timer up to 12 hours, removing the AM/PM with css updates is unreliable as this seems the only way to approach it ::-webkit-datetime-edit-ampm-field { display: none;} . AM/PM is still displaying in my tests. I'm doubting that js/css can be used for a duration input polyfill .
10:20
<annevk>
stephanluis: a quick search yields https://nadchif.github.io/html-duration-picker.js/
10:21
<stephanluis>
I've looked at that it doesn't maintain the time input functionality, on the demo you can see additional buttons are required.
10:27
<annevk>
You could remove those presumably. And what input type=time is largely depends on implementations. Anyway, I recommend reaching out to Open UI. I don't think I can help.
10:32
<stephanluis>
But that's the problem, time input is based on browser implementations because there are so many international formats for time. The standard needs (is missing) is straightforward hours minutes, seconds -- with decimals -- control that browsers implement for the universal part of time.
10:41
<stephanluis>
annevk: and there doesn't seem to be a 'follow the usual path' of writing a polyfill to demonstrate the need because browsers have such 'in baked' and diverse implementations.
11:00
<stephanluis>
annevk: I hope WHATWG sees the need to do something. Let me know if I can help in any way. Thanks.