Daniel Ethridge

[not sure where to ask this] I'm wondering if there is an even more elegant approach syntax for these different types of accesses (normal `a.b`, optional `a?.b`, and infallible `a!.b`)....

I came across this issue while searching for existing solutions for part of a UI library I'm writing. In essence, the DOM needs a way to move a child node...

> Please go read the past discussion in this issue as well as [whatwg/html#5484](https://github.com/whatwg/html/issues/5484) before making any suggestions ... It's really counterproductive to keep repeating the same discussion every 2-3...

Sorry for the miscommunication, I meant atomic move among siblings, the primitive operation enabling the proposal. The animation problem that the Mithril maintainer mentioned would be orthogonal to this -...

Maybe I misunderstood the problem, but here are my immediate thoughts: Ideally, the DOM would provide a `document.nodesWithinRect()` sort of like [`document.elementsFromPoint`](https://developer.mozilla.org/en-US/docs/Web/API/Document/elementsFromPoint), and then we could just test if there...

@jordanl17 don't edit without commenting why — it's now inaccurate, the original `"a b"` is correct

Sorry about the late reply Kethan. Bruh is a bit unlike react in some ways; that `count.value` access would only run once (because it just gets the _current_ value of...

I'm not quite sure how to answer that because there is no component lifecycle, so there is no component unmounting. This may change in the future, but I'm trying to...

There's also this related PR that's been on hold https://github.com/microsoft/TypeScript/pull/58084