[Webkit-unassigned] [Bug 94274] Move Shadow DOM inspection feature out from experiments if Shadow DOM flag is enabled

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Aug 19 18:36:30 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=94274





--- Comment #6 from Hayato Ito <hayato at chromium.org>  2012-08-19 18:37:05 PST ---
Got it. Thank you.
I still think a capability test in JS is a most reliable way to judge it. :)

(In reply to comment #5)
> > I am wondering why we need DOM.supportsShadowDOM.
> > I guess DOM.supportsXXX is a established convention, but the following is enough, isn't it?
> > 
> > var supportsShadowDOM = window.WebKitShadowRoot || window.ShadowRoot
> It's safer to tell it from C++ side since ShadowDOM availability can be
> switched per-frame (domain) and Inspector has its own page/frame
> which is different from the page under debug.
> 
> But in reality, no browser will use such per-frame flag control and 
> it will be OK just to check WebKitShadowRoot :-)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list