Chrome Version: ToT r465173
OS: Linux/all
What steps will reproduce the problem?
(1) Apply the attached patch
(2) Run that layout test
What is the expected result?
Pass the test, or at least don't crash.
What happens instead?
It crashes.
I discovered this while investigating Issue 710184. I haven't investigated this in depth but my theory is this: Chrome uses a private to store the custom element's registered name on the constructor so registering it twice overwrites that property. As a consequence using it in the original context crashes when it fails to find a definition.
Those private properties should be per context, not per isolate.
|
Deleted:
failing-test.patch
1.1 KB
|
Comment 1 by dominicc@chromium.org
, Apr 19 2017