dom
dom copied to clipboard
whatwg
DOM Standard
### What is the issue with the DOM Standard? The `AbortSignal.timeout(...)` method provided us with a nice functional mechanism to abort an operation after a given period of time and...
I think there are valid use cases for DOM APIs like `DOMParser`, `XMLSerializer`, `document.implementation.createDocument()` etc. to be available in web workers. I don't mean having direct access to the current...
This calls the get Trusted Types-compliant attribute value algorithm from Trusted Types (https://github.com/w3c/trusted-types/pull/418) from attribute's change, append, and replace. Changed the signature of `setAttribute` and `setAttributeNS` to accept Trusted Types...
### What problem are you trying to solve? Chrome (@domfarolino, @noamr, @mfreed7) is interested in pursuing the addition of an atomic move primitive in the DOM Standard. This would allow...
This issue was [raised as part of the Chromium review](https://chromium-review.googlesource.com/c/chromium/src/+/5239277/comment/3d66eb39_1ccfcf33/) of the implementation of `clonable`. The question is what should happen here: ```javascript const shadow = host.attachShadow({mode: 'open', clonable: true});...
### What is the issue with the DOM Standard? See https://github.com/whatwg/html/issues/10107 for context. But some fields of `ShadowRoot` feel like they could easily be made mutable: - `delegatesFocus` - `clonable`...
The [clone](https://dom.spec.whatwg.org/#concept-node-clone) algorithm in the DOM spec currently describes the cloning algorithm when the "clone children" flag is set as recursively cloning the children and then appending them to the...
- [ ] At least two implementers are interested (and none opposed): * … * … - [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:...
Developers seem to assume that `connectedCallback` means the element's contents will be present. This isn't helped by browser differences ([demo](https://wc-connected-test.glitch.me)). Safari & Firefox get it wrong and show some element...
### What problem are you trying to solve? What if DOM elements could provide fallback, proxy, replacement, substitute, or surrogate elements for themselves? This would enable scenarios including shadow tree...
