diff options
author | bors-servo <lbergstrom+bors@mozilla.com> | 2020-02-14 09:43:10 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-02-14 09:43:10 -0500 |
commit | 4f36472b6fed75568c651cbbeecc6678791018a9 (patch) | |
tree | 9d2235de6a1d83fc1b1292f57f9bf072b8d8b50d /components/script/dom/performanceobserver.rs | |
parent | 38adec64e15f1b323bffb56ea5e4e4f1da686a0c (diff) | |
parent | 5ef335895138bff8288a840c39779dda760dfbec (diff) | |
download | servo-4f36472b6fed75568c651cbbeecc6678791018a9.tar.gz servo-4f36472b6fed75568c651cbbeecc6678791018a9.zip |
Auto merge of #25674 - pshaughn:selection, r=jdm
Selection DOM interface (but not actual UI selections)
This is work towards #7492.
I put new tests in the mozilla-specific directory rather than the main tree because I'm not sure how upstreamable they are; I'd like opinions on that point.
This adds a new exposed interface, which I understand from tests/mozilla/interfaces.html is something requiring specific approval from someone allowed to give that approval.
Things that aren't done here:
- The spec doesn't describe what selection/script-and-style-elements.html wants, and what it wants seems to require some sort of layout query.
- Actual UI interactions are not present at all; selection.rs has a few TODOs saying which methods I believe the eventual UI code should call for what actions, but there are a lot of fine points here that I don't know about.
- I haven't touched Node; you can ask if a node's in the Selection's Range the same way you'd ask about any other Range, but there's not a faster path just for selection layout.
Diffstat (limited to 'components/script/dom/performanceobserver.rs')
0 files changed, 0 insertions, 0 deletions