[wpt-sync] Sync PR 20465 - Quick attempt to outlaw recursive custom element constructions
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox73 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 20465 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/20465
Details from upstream follow.
Mason Freed <masonfreed@chromium.org> wrote:
Quick attempt to outlaw recursive custom element constructions
Essentially, because the constructors are called synchronously,
the custom element state never gets changed to kCustom at [1],
so there is no easy way to just check the state at the top as
the spec ([2]) states in step 4.13.5.1. This CL looks at the
custom element construction stack, and looks for a null top
element, which is the case when the existing element
recursively calls the same constructor.[1] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/html/custom/custom_element_definition.cc?rcl=07d3d555040a175bfdf35ccc008939258273e6bd&l=212
[2] https://html.spec.whatwg.org/multipage/custom-elements.html#upgradesBug: 966472
Change-Id: I76e88c0b70132eee2482c304ef9e727ae1fe8fc7
Reviewed-on: https://chromium-review.googlesource.com/1931644
WPT-Export-Revision: 01092bc60a19bf6bdf303ee34960b5dbcf7b222b
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/99e8822752ad
https://hg.mozilla.org/mozilla-central/rev/80137062b7a2
Description
•