- From: Tab Atkins Jr. <notifications@github.com>
- Date: Mon, 06 Mar 2023 14:29:08 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/pull/1168@github.com>
https://dom.spec.whatwg.org/#concept-range-start > A range has two associated boundary points — a **start** and **end**. These definitions are correctly namespaced, but the words are still pretty generic, which has two problems: * It's so generic, it makes some of the more complex sentences in the DOM spec harder to read because the association of these words to the range object is implicit rather than immediately obvious. * It conflicts with other uses of [=start=] and [=end=], such as the (much more common) usage of CSS's "start" and "end" directions, which then always need to specify `[=CSS/start=]`. (There are other definitions of plain "start"/"end" in Bikeshed's db also, but none of them are exported so they don't interfere.) Would you mind renaming to "range start" and "range end"? This would also simplify your markup a bit - right now every usage of the terms is written as `<a for=range>start</a>`; after this fix they'd be `[=range start=]`. This PR does so, and I believe is an editorial improvement. You can view, comment on, or merge this pull request online at: https://github.com/whatwg/dom/pull/1168 -- Commit Summary -- * Rename Range's 'start' and 'end' to 'range start' and 'range end'. -- File Changes -- M dom.bs (115) -- Patch Links -- https://github.com/whatwg/dom/pull/1168.patch https://github.com/whatwg/dom/pull/1168.diff -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1168 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1168@github.com>
Received on Monday, 6 March 2023 22:29:20 UTC