whatwg/dom on Hacker News

…developers and users. There is an alternative suggestion to DOM parts which might be a better bet: https://github.com/whatwg/dom/issues/736

comment by llcooliovice · 2025-06-27 · in The time is right for a DOM templating API

…HTML elements less, which is a modern regression that has severely hampered extensions/user agency. https://github.com/whatwg/dom/pull/1307

comment by jauntywundrkind · 2025-03-07 · in Introducing command And commandfor In HTML

…i've also been working with the chrome team to get a feature added they are calling "atomic moves": https://github.com/whatwg/dom/issues/1255 this would allow us to move elements around in the DOM without losing things like play state or…

comment by recursivedoubts · 2024-04-25 · in A Response to "Have Single-Page Apps Ruined the Web?" (2021)

Domenic Denicola (aka the man who ruined promises) probably will as well. https://github.com/whatwg/dom/issues/67

comment by pwdisswordfishc · 2023-07-17 · in Using XPath in 2023

…of shadow DOM have been undersung. And Declarative Shadow DOM makes it way more useful. [1]: https://github.com/whatwg/dom/issues/831#issuecomment-585489...

comment by nolanl · 2023-02-14 · in Declarative Shadow DOM

…Tests 23 & 25 require a specific error type that has since been changed in that circumstance: https://github.com/whatwg/dom/issues/319#ref-commit-94dd371 Test 35 requires root elements to not match :first-child, and the spec was changed to…

comment by mminer237 · 2022-03-30 · in SerenityOS Browser now passes the Acid3 test

…2: https://github.com/lit/lit-element 3: https://stenciljs.com/ 4: https://github.com/whatwg/dom/issues/831

comment by runarberg · 2021-06-09 · in Real-world CSS vs. CSS-in-JS performance comparison

A related proposal can also be found here: https://github.com/whatwg/dom/issues/270 I'm curious why this hasn't made it to the browser yet and doesn't seem to be explored very seriously. So many web-frameworks revolve around trying to…

comment by apexedison · 2021-04-03 · in Proposal to add efficient DOM diffing to browser

…competing arguments how it is useful. If problem is usability we should address it first [2]. [1] https://github.com/whatwg/dom/issues/903#issuecomment-707828... [2] https://news.ycombinator.com/item?id=24766845

comment by sergeykish · 2020-10-13 · in WhatWG: Proposal – Update XPath to at least v2.0

…our pipeline are in maintenance mode and we would love to eventually deprecate and remove them > -- https://github.com/whatwg/dom/issues/903#issuecomment-707748... Given Chrome's status as the new IE6 in terms of market share and outsized…

comment by lucideer · 2020-10-13 · in WhatWG: Proposal – Update XPath to at least v2.0

…expect I may be using more than once or twice, I see about more precise whitelisting in uMatrix. ² https://github.com/whatwg/dom/issues/831

comment by chrismorgan · 2020-07-17 · in Shoelace 2.0 release: UI toolkit that works with all frameworks or none at all

To expand a bit more: > Wikipedia gives this as an example of a standard that changed: https://github.com/whatwg/dom/issues/319 That's the reason why tests 23 and 25 fail (both because of the "wrong" exception being thrown);…

comment by gsnedders · 2020-06-13 · in Flow browser passes the Acid tests

…especially for mobile browsers." Wikipedia gives this as an example of a standard that changed: https://github.com/whatwg/dom/issues/319 Edit: there's an updated version at http://wpt.live/acid/acid3/test.html

comment by sp332 · 2020-06-13 · in Flow browser passes the Acid tests

…includes helper scripts so working group members can run 'make review' and publish the latest draft https://github.com/whatwg/dom/blob/master/Makefile

comment by hackermailman · 2019-10-13 · in Ask HN: What is a good way to coordinate online for a technical working group?

…Shadow DOM element https://github.com/w3c/webcomponents/blob/gh-pages/proposals... (rejected https://github.com/whatwg/dom/issues/510 ). Yeah, you can pre-render them without the Shadow DOM. Then if you want to make those chunks of HTML…

comment by JackuB · 2019-04-12 · in Web Components could replace frontend frameworks?

…There are 3 things that are known to fail. Two of them are related to one change (see https://github.com/whatwg/dom/issues/319#issuecomment-296345... for details on that change). The third test is one where Acid3 mandates something that…

comment by jcranmer · 2019-01-18 · in The Acid3 Test (2008)

…access to DOM without copying this wouldn’t actually be that stupid. It might be possible some day: https://github.com/whatwg/dom/issues/270

comment by deno · 2018-01-02 · in Show HN: Sapper.js – towards a better web app framework

…those decisions mean. Here is a very simplified description of this problem years after the fact: https://github.com/whatwg/dom/issues/102 It is important to understand the DOM wasn't created for HTML. The DOM, starting with DOM level 2,…

comment by austincheney · 2017-12-14 · in HTML 5.2 Recommendation

…that a 'first-child' have a parent, and chrome's behaviour matches. The second is discussed here https://github.com/whatwg/dom/issues/319 Roughly, when interpreting qualified names, Chrome is throwing InvalidCharacterErrors when the acid…

comment by wolfgke · 2017-12-14 · in HTML 5.2 Recommendation

…that a 'first-child' have a parent, and chrome's behaviour matches. The second is discussed here https://github.com/whatwg/dom/issues/319 Roughly, when interpreting qualified names, Chrome is throwing InvalidCharacterErrors when the acid…

comment by systoll · 2017-09-15 · in Ask HN: Why don't modern Chrome and Firefox pass the Acid3 test anymore?

…that use it is the main place so far. There is also discussion about maybe using the same switch in https://github.com/whatwg/dom/issues/278 if it turns out that too many pages assume "not webkit" means XMLDocument.load exists. It could be…

comment by bzbarsky · 2016-10-28 · in A Quantum Leap for the Web