| 19:35 | <oliverdunk> | Would it make sense to update the definition of a date string, to allow a single digit for specifying the month/date? It'd be nice to remove the need for zero padding, when code setting the attribute doesn't have it by default. |
| 19:35 | <oliverdunk> | The particular use case I have is when programatically setting the max attribute on a date input. |
| 20:07 | <annevk> | oliverdunk: it'd add parser complexity and I'm not sure it'd help with readability either |
| 20:22 | <oliverdunk> | annevk: It seemed like the "parse a date component" section would only need a small tweak, and I hoped the difference in readability was negligible. I trust your gut though, thanks for replying. |
| 23:34 | <MikeSmith> | botie, inform rniwa does the Safari version data at https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/slot#Browser_compatibility make any sense at all? It claims the "slot" attribute was “Implemented with the vendor prefix: -webkit-” in Safari 10 — though without the prefix in iOS Safari. It as never actually implemented as an attribute named "-webkit-slot" anywhere, right? |
| 23:34 | <botie> | will do |