New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 831182 link

Starred by 1 user
Status: WontFix
Owner:
█ kochi@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
hayato@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Google I/O 2015 site broken by removal of multiple shadow roots

Project Member Reported by pdr@chromium.org, Apr 10 2018 
Site: https://events.google.com/io2015/

This site now throws errors and is unusable. I bisected this down to:
Disable multiple shadow roots
https://chromium.googlesource.com/chromium/src/+/bdf17920ad6a1d02c97159fb0e986eaf2c7fc30f

This site works in Safari and Firefox but not Chrome. Are they using an old library that we might be able to update?

This bug may be WONTFIX, just wanted to file in case it's something easy to fix.

Comment 1 by kochi@chromium.org, Apr 11 2018 

Thanks for the interesting report.
I guess once we have removed all Shadow DOM V0 APIs, it will work again.
Let me check if it works with --disable-blink-features=ShadowDOMV0.

Comment 2 by kochi@chromium.org, Apr 11 2018

Status: WontFix (was: Assigned)
As I anticipated, the site (https://events.google.com/io2015/ ) worked
with --disable-blink-features=ShadowDOMV0.

So the site is working as expected (from our perspective :-) ), and if
all Shadow DOM V0 stuff is ripped out, it falls back to the polyfill,
then it will work like Firefox/Safari.

Closing as wontfix.


So... regarding how you notice where the site is broken, it's multiple
shadow's fault... on the console, I found the following message:

Uncaught DOMException: Failed to execute 'createShadowRoot' on 'Element': Shadow root cannot be created on a host which already hosts a shadow tree.
    at HTMLElement.shadowFromTemplate (https://events.google.com/io2015/elements/elements.js:14:27259)
    at HTMLElement.parseDeclaration (https://events.google.com/io2015/elements/elements.js:14:27032)
    at HTMLElement.parseDeclarations (https://events.google.com/io2015/elements/elements.js:14:26892)
    at HTMLElement.makeElementReady (https://events.google.com/io2015/elements/elements.js:14:26170)
    at HTMLElement.createdCallback (https://events.google.com/io2015/elements/elements.js:14:25743)
    at HTMLElement.registerPrototype (https://events.google.com/io2015/elements/elements.js:15:14754)
    at HTMLElement.register (https://events.google.com/io2015/elements/elements.js:15:11981)
    at HTMLElement._register (https://events.google.com/io2015/elements/elements.js:15:19354)
    at Object.flush (https://events.google.com/io2015/elements/elements.js:15:16949)
    at Object.ready (https://events.google.com/io2015/elements/elements.js:15:17096)

But without knowledge of how shadow dom v0 is being deprecated, it's hard to identify the cause
is it from this console output.
►

Sign in to add a comment