Adding the Range as a feature #1380
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| name: Range | ||
| description: The Range interface represents a fragment of a document that can contain nodes and parts of text nodes. | ||
|
Collaborator
There was a problem hiding this comment.
I we may need a DOM feature for most old parts of https://dom.spec.whatwg.org/ that other specs depend on. @ddbeck WDYT?
Collaborator
There was a problem hiding this comment. Until we're backed into a corner, I think we ought to put such interfaces with their most longstanding dependent features (e.g., unless someone has an older use-case, That said, if there's no such feature or it has use alone—supposing I'm wrong about |
||
| spec: https://w3c.github.io/DOM-Parsing/ | ||
| compat_features: | ||
| - api.Range | ||
| - api.Range.createContextualFragment | ||
| - api.Range.Range | ||
| - api.Range.cloneContents | ||
| - api.Range.cloneRange | ||
| - api.Range.collapse | ||
| - api.Range.collapsed | ||
| - api.Range.commonAncestorContainer | ||
| - api.Range.compareBoundaryPoints | ||
| - api.Range.comparePoint | ||
| - api.Range.deleteContents | ||
| - api.Range.endContainer | ||
| - api.Range.endOffset | ||
| - api.Range.extractContents | ||
| - api.Range.insertNode | ||
| - api.Range.intersectsNode | ||
| - api.Range.isPointInRange | ||
| - api.Range.selectNode | ||
| - api.Range.selectNodeContents | ||
| - api.Range.setEnd | ||
| - api.Range.setEndAfter | ||
| - api.Range.setEndBefore | ||
| - api.Range.setStart | ||
| - api.Range.setStartAfter | ||
| - api.Range.setStartBefore | ||
| - api.Range.startContainer | ||
| - api.Range.startOffset | ||
| - api.Range.surroundContents | ||
| - api.Range.toString | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,104 @@ | ||
| # Generated from: range.yml | ||
| # Do not edit this file by hand. Edit the source file instead! | ||
|
|
||
| status: | ||
| baseline: high | ||
| baseline_low_date: 2018-04-30 | ||
| baseline_high_date: 2020-10-30 | ||
| support: | ||
| chrome: "29" | ||
| chrome_android: "29" | ||
| edge: "17" | ||
| firefox: "24" | ||
| firefox_android: "24" | ||
| safari: "8" | ||
| safari_ios: "8" | ||
| compat_features: | ||
| # baseline: high | ||
| # baseline_low_date: 2015-07-29 | ||
| # baseline_high_date: 2018-01-29 | ||
| # support: | ||
| # chrome: "1" | ||
| # chrome_android: "18" | ||
| # edge: "12" | ||
| # firefox: "1" | ||
| # firefox_android: "4" | ||
| # safari: "1" | ||
| # safari_ios: "1" | ||
| - api.Range | ||
| - api.Range.cloneContents | ||
| - api.Range.cloneRange | ||
| - api.Range.collapse | ||
| - api.Range.collapsed | ||
| - api.Range.commonAncestorContainer | ||
| - api.Range.compareBoundaryPoints | ||
| - api.Range.createContextualFragment | ||
| - api.Range.deleteContents | ||
| - api.Range.endContainer | ||
| - api.Range.endOffset | ||
| - api.Range.extractContents | ||
| - api.Range.insertNode | ||
| - api.Range.selectNode | ||
| - api.Range.selectNodeContents | ||
| - api.Range.setEnd | ||
| - api.Range.setEndAfter | ||
| - api.Range.setEndBefore | ||
| - api.Range.setStart | ||
| - api.Range.setStartAfter | ||
| - api.Range.setStartBefore | ||
| - api.Range.startContainer | ||
| - api.Range.startOffset | ||
| - api.Range.surroundContents | ||
| - api.Range.toString | ||
|
|
||
| # baseline: high | ||
| # baseline_low_date: 2017-04-05 | ||
| # baseline_high_date: 2019-10-05 | ||
| # support: | ||
| # chrome: "1" | ||
| # chrome_android: "18" | ||
| # edge: "15" | ||
| # firefox: "1" | ||
| # firefox_android: "4" | ||
| # safari: "3" | ||
| # safari_ios: "1" | ||
| - api.Range.isPointInRange | ||
|
|
||
| # baseline: high | ||
| # baseline_low_date: 2017-04-05 | ||
| # baseline_high_date: 2019-10-05 | ||
| # support: | ||
| # chrome: "29" | ||
| # chrome_android: "29" | ||
| # edge: "15" | ||
| # firefox: "24" | ||
| # firefox_android: "24" | ||
| # safari: "8" | ||
| # safari_ios: "8" | ||
| - api.Range.Range | ||
|
|
||
| # baseline: high | ||
| # baseline_low_date: 2018-04-30 | ||
| # baseline_high_date: 2020-10-30 | ||
| # support: | ||
| # chrome: "1" | ||
| # chrome_android: "18" | ||
| # edge: "17" | ||
| # firefox: "1" | ||
| # firefox_android: "4" | ||
| # safari: "3" | ||
| # safari_ios: "1" | ||
| - api.Range.comparePoint | ||
|
|
||
| # baseline: high | ||
| # baseline_low_date: 2018-04-30 | ||
| # baseline_high_date: 2020-10-30 | ||
| # support: | ||
| # chrome: "1" | ||
| # chrome_android: "18" | ||
| # edge: "17" | ||
| # firefox: "17" | ||
| # firefox_android: "19" | ||
| # safari: "3" | ||
| # safari_ios: "1" | ||
| - api.Range.intersectsNode |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we haven't got an answer to whether this should standalone yet, but I also don't want to let this sit idle for forever, here's my idea for how to proceed with this:
Let's move this in to the
draftfolder, add the draft date, and add a comment that links to this PR's discussion. That way, when we do get an answer to whether or not we need some "foundational DOM" feature (or features), then we have at least this part of the work documented somewhere.