You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 24, 2021. It is now read-only.
http://chromeexperiments.com should show more than 57 elements in Chrome, where the shadow dom works. It should continue to report 53 in Edge where nothing shows up.
The text was updated successfully, but these errors were encountered:
Investigating this further shows that solving this issue is analogous to be able to crawl content in iframes, security considerations excepted. We need to ask each element for its possible shadow dom, and if we find one we have to queue the execution of both the DOM and CSS analysis on that "document".
We can try to reuse the same CSSResults instance and accumulate the results between the runs, but we have to make sure that actually works. Right now some subsections of the data collection "erase" parts of the data structure while they create it. Supporting multi-document-roots runs would require updating this to make sure we only "add" or "increment" stuff, and that we never "set" result data.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
http://chromeexperiments.com should show more than 57 elements in Chrome, where the shadow dom works. It should continue to report 53 in Edge where nothing shows up.
The text was updated successfully, but these errors were encountered: