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.
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
refactor: make element spec processing more cosistent #4093
refactor: make element spec processing more cosistent #4093
Changes from 2 commits
0c1cbaa
ab49aa6
4c0fbba
15fffd0
e50d947
d927ab1
9c48f1c
0a98679
ff1a0b3
e61e736
4a9e9e7
e6f3f5f
2229271
1a2c0ed
b200ba2
e29263f
56029ed
71a1323
d1b07e1
c59ad63
9c003a1
85afbe9
ec70f34
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The original test was
configure
ing in the top frame but not the child frame. This isn't supported and doesn't provide the protectionnoHtml
is intended to (the thing that the test after this one is verifying). However, previously, the original test worked despite testing an unsupported configuration because there was an extra round trip throughDqElement
in the top frame involved that no longer exists.I think it's preferable to break the old pattern and demand that configure must be called consistently in each frame, so I changed the test rather than forcing a top-frame-only
noHtml
configure to suppresshtml
properties from child frame results, but if that feels too concerning for backcompat reasons you could address it by adding anaudit.noHtml
test into theprocess-aggregate.js
code that's filling inhtml
fromnode.source
.