Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make HTMLFormControlsCollection rooted at the form's root, not rooted at the form itself #25719

Merged
merged 1 commit into from Feb 11, 2020

Conversation

@pshaughn
Copy link
Member

pshaughn commented Feb 10, 2020

We'd been misreading the first line of https://html.spec.whatwg.org/#dom-form-elements. The collection needs to be rooted higher than the form itself, so it can contain form controls elsewhere in the document with a form= content attribute. It is, as far as I can tell, unspecified whether "rooted at the form's root" is meant to live-update to a new root if the form is moved to another tree, and I'm assuming it doesn't have to.


  • ./mach build -d does not report any errors
  • ./mach test-tidy does not report any errors
  • These changes fix #25711
  • There are tests for these changes
@highfive
Copy link

highfive commented Feb 10, 2020

Heads up! This PR modifies the following files:

  • @asajeffrey: components/script/dom/htmlformcontrolscollection.rs
  • @KiChjang: components/script/dom/htmlformcontrolscollection.rs
@jdm
Copy link
Member

jdm commented Feb 10, 2020

@bors-servo
Copy link
Contributor

bors-servo commented Feb 10, 2020

📌 Commit 0eeb075 has been approved by jdm

@highfive highfive assigned jdm and unassigned nox Feb 10, 2020
@bors-servo
Copy link
Contributor

bors-servo commented Feb 11, 2020

Testing commit 0eeb075 with merge 3725273...

bors-servo added a commit that referenced this pull request Feb 11, 2020
Make HTMLFormControlsCollection rooted at the form's root, not rooted at the form itself

<!-- Please describe your changes on the following line: -->
We'd been misreading the first line of https://html.spec.whatwg.org/#dom-form-elements. The collection needs to be rooted higher than the form itself, so it can contain form controls elsewhere in the document with a form= content attribute. It is, as far as I can tell, unspecified whether "rooted at the form's root" is meant to live-update to a new root if the form is moved to another tree, and I'm assuming it doesn't have to.

---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [X] These changes fix #25711

<!-- Either: -->
- [X] There are tests for these changes

<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->

<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
@bors-servo
Copy link
Contributor

bors-servo commented Feb 11, 2020

☀️ Test successful - status-taskcluster
Approved by: jdm
Pushing 3725273 to master...

@bors-servo bors-servo merged commit 0eeb075 into servo:master Feb 11, 2020
2 checks passed
2 checks passed
Community-TC (pull_request) TaskGroup: success
Details
homu Test successful
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.