Do not switch to V1 cascade order if shadow root is UA shadow
Once V1 shadow root is attached to a document, we switch cascading order to V1-compliant mode from V0-legacy mode, but recent migration of UA shadows from V0 to V1 caused the cascading order switch without explicitly creating author V1 shadow root. This happens only in the following scenario: 1. An element with V1 UA shadow is created in another document 2. The element with V1 UA shadow is adopted to the document. In other cases, internal APIs such as EnsureUserAgentShadowRoot() or CreateUserAgentShadowRoot() does not share the same code path for web-facing Element.attachShadow(), the cascading order is not affected. Bug: 801938, 787717 Change-Id: I93e41e8f6f0acda4f3804e1ef316da205454b62f Reviewed-on: https://chromium-review.googlesource.com/875585Reviewed-by:Rune Lillesveen <futhark@chromium.org> Commit-Queue: Takayoshi Kochi <kochi@chromium.org> Cr-Commit-Position: refs/heads/master@{#530738}
Showing
Please register or sign in to comment