| 13:21 | <wanderview> | JakeA: looks like Edge 16 shipped abortable fetch() first... sadly the glitch demo doesn't work since they don't support TextDecoder() |
| 13:47 | <wanderview> | JakeA: I remixed it to work... https://fetch-abort-demo-edge.glitch.me/ |
| 13:47 | <wanderview> | I also had to drop the pre.append() stuff |
| 14:11 | <gsnedders> | did someone not have a semi-maintained fork of Anolis somehwere? |
| 14:12 | <gsnedders> | Ah, Ms2ger, at https://bitbucket.org/ms2ger/anolis |
| 15:07 | <JakeA> | wanderview: ohhh cheers! Will tweet that when I'm back from holidays |
| 15:11 | <wanderview> | JakeA: oh, right... enjoy your family not-chrome-dev-summit event! |
| 17:32 | <wanderview> | and safar TP 42 seems to have initial bits landing for fetch() abort as well |
| 17:32 | <wanderview> | safari |
| 18:23 | <jsx> | Many docs in MDN lists type as DOMString where the specs says USVString. Are they interchangeable since they both indicate a JavaScript String? |
| 18:30 | <TabAtkins> | jsx: Technically a USVString doesn't allow unpaired surrogate codepoints, so it's not the full value space of DOMString. |
| 18:31 | <TabAtkins> | But for all strings you're ever going to construct for actual text, yeah, they're equivalent. (Only when you're using JS strings as a byte-storage type, or have some weirdness like a text stream that got interrupted partway thru, will you see an unpaired surrogate show up.) |
| 18:35 | <jsx> | TabAtkins: Hmm, ok. So I'll leave it be. |
| 18:35 | <jsx> | Thanks! |
| 18:36 | <TabAtkins> | (CSSOM is currently using CSSOMString, which is defined as `(DOMString or USVString)`, because we want to use USVString for all "real text", but some engines currently don't have good optimizations for applying that restriction (while others do).) |
| 18:37 | <gsnedders> | jsx: also USVString is a relatively new thing |
| 18:38 | <jsx> | Excuse the noob question: So is USVString a subset of DOMString? |
| 18:38 | <TabAtkins> | Yes. |
| 18:38 | <TabAtkins> | Like I said, it's a DOMString that just doesn't allow unpaired surrogates in itself. |
| 18:38 | <jsx> | Ok.. |
| 18:38 | <TabAtkins> | (Aka only allows actual unicode codepoints, not arbitrary bytes.) |
| 18:39 | <Mek> | not sure "allow" is the right word. You can still pass strings with unpaired surrogates to methods accepting USVStrings for example, they just get removed before the underlying algorithms handle the strings |
| 18:39 | <TabAtkins> | Ah, I couldn't remember if violating the restriction threw an error or just converted. |
| 18:40 | <Mek> | https://heycam.github.io/webidl/#dfn-obtain-unicode is how a DOMString is converted to a USVString, no throwing in there |
| 19:26 | <Domenic> | +1 Mek |
| 19:26 | <Domenic> | I found https://infra.spec.whatwg.org/#strings but to be fair I did have a large hand in helping write it |