| 08:09 | <annevk> | In retrospect [SameAs=href] USVString toString(); or some such might have been better |
| 08:10 | <annevk> | WebKit has something like that so you can implement getters that return the same thing once and it's lovely |
| 12:58 | <annevk> | https://twitter.com/robpalmer2/status/1658914059578744835 made me think of a similar request I had seen for AbortSignal but I can't find it. Something like AbortSignal.withAborter() -> { signal, aborter }. |
| 17:02 | <Jeffrey Yasskin> | Is the advice in https://webidl.spec.whatwg.org/#idl-USVString that "Specifications should only use USVString for APIs that perform text processing .... When in doubt, use DOMString." still the state of the art? In cases where we expect most of the input to be text instead of 16-bit numbers, it feels like a recipe for subtle implementation bugs if an implementation round-trips a lone surrogate through UTF-8 instead of WTF-8. |