Kevin Gibbons

Any progress on this? We're adopting this font for [the JavaScript specification](https://tc39.es/ecma262/) and this is the only significant painpoint.

The JS proposal has landed in the JS specification, with implementations shipping in Chrome and Safari and IIRC underway in Firefox.

Ideally only when you've selected multiple lines, though.

Yeah I was imagining [hijacking the copy](https://developer.mozilla.org/en-US/docs/Web/API/Element/copy_event).

Editors are OK with landing this but still need to review for correctness.

The cause here is that array iterators aren't closable, unlike generators. I think that was probably a mistake; they should have been, which would have made these consistent (by having...

`AsyncIterator.from` will accept strings because `Iterator.from` does. But do note that it's specifically a coercion method. For something like `ReadableStream.from`, which is also a coercion method, you may wish to...

Personally I would specify this by making `async iterable` reject strings, and then adding `or USVString` to those places which should accept strings, just to ensure that future users of...

Related: [proposal to add Observables and make EventTarget observable](https://github.com/domfarolino/observable). The `once` case would be `await target.on('event').first()`. The iterator case would require [a new helper](https://github.com/domfarolino/observable/issues/33), and a choice of queuing strategy,...

What's the actual difference? The thing the OP proposes is > `EventTarget.once() returns a Promise that is resolved the next time the event is dispatched. which sounds exactly like `first`...