- From: smaug---- <notifications@github.com>
- Date: Tue, 18 Feb 2025 13:43:21 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 18 February 2025 21:43:25 UTC
smaug---- left a comment (whatwg/dom#1268) I think that would work for setNameItem* and setAttributeNode*. Current code in Gecko does "If attr’s element is neither null nor element" before and after, and maybe doing it only after is good enough. right @fred-wang ? Attr.value/.nodeValue/.textContent should do validation (if there is element) too before modifying the value. (chromium and webkit seem to do something else, assuming I'm reading the code correctly) Element.setAttribute/Element.setAttributeNS in the PR needs some tweaking too. Implementations don't necessarily create Attr nodes when those APIs are used, but if they do, what happens if TT callback moves the Attr away. As fred-wang mentioned earlier, implementations already just create a new attribute on the element. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1268#issuecomment-2666991057 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1268/c2666991057@github.com>
Received on Tuesday, 18 February 2025 21:43:25 UTC