Darien Maillet Valentine

Both of these elements have special associated [tokenizer states](https://html.spec.whatwg.org/#script-data-state) that would collide with the declarative syntax for shadow root. They also have existing initialization/change behaviors. For script in particular it...

If API additions along these lines become a thing, I hope that API can be devised in a way that accounts for race/all patterns. I've used homegrown promise/async-iterable DOM event...

> but in most cases it shouldn't matter That's true - probably doesn't matter for indexeddb success/error\* for example - but it seems you can silently accrue _a lot_ of...

Spitballing follows. Not sure if maybe some of these are already unavailable due to collision given how many EventTarget subclasses there are. Single - `.when("blur")` - `.advent("hashchange")` - `.eventual("keydown")` /...

> If there are any sites out there which rely on the full reparenting logic, they could become broken. The disconnectedCallback and connectedCallback reactions fire on custom elements when nodes...

Before the window here closes, as someone who isn’t here because of HN :), I thought it might be helpful to add a data point. I’ve also used XPath for...

> I expected developers to not use these classes. Perhaps it’s less common than I thought. I’ve used it fairly often over the years — being able to skip subtrees...

@annevk I think that it would also be reasonable to disallow lone surrogates. It’s [possible to get them into the input stream with document.write](https://html.spec.whatwg.org/multipage/parsing.html#parse-error-surrogate-in-input-stream) and they’re accepted as chardata unchanged...

> flawed construct for it's intended purpose The API seems to cover more than one use case and control flow pattern. Separation of the controller and signal allows sharing the...

@jakearchibald fwiw I think the doAbortable model shown in that thread is, at best, moving an existing problem around. The need is to “decorate await”, not to “decorate async”, and...