- From: Krzysztof Maczyński via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Nov 2021 03:44:31 +0000
- To: public-css-archive@w3.org
Well, that's where WHATWG went with it (though I don't see a technical reason for changing the established term, however they just seem to get off on spurious deviations), while W3C specs (like e.g. XQuery) use (and sometimes extend as needed) document order. But you're right, it's for whole nodes. What's needed here are [boundary-points](https://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-Position) and [Comparing Range Boundary-Points](https://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-Comparing) restricted to collapsed Ranges. -- GitHub Notification of comment by ByteEater-pl Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6839#issuecomment-981266460 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 November 2021 03:44:32 UTC