[Webkit-unassigned] [Bug 103208] Don't use ComposedShadowTreeWalker in NodeRenderingContext when SHADOW_DOM is not enabled
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Nov 26 18:03:14 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=103208
Hajime Morrita <morrita at google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |webcomponents-bugzilla at chro
| |mium.org
Blocks| |103339
--- Comment #9 from Hajime Morrita <morrita at google.com> 2012-11-26 18:05:24 PST ---
For performance, we should definitely get rid of the regression. I'll take a look to make this patch work with <details>.
For binary size, it's infeasible for now to hide whole Shadow DOM things behind a flag. It will result tons of ifdefs and hurts the code readability. Sine it replaces certain renderer implementations, it can taken as a nice-to-have WebCore plumbing. That being said, I agree that some more Shadow DOM/Web Components implementation can be moved behind the flag. That will be tracked by a bug 103339.
On the flag name, please let us use SHADOW_DOM. The API standard is named like that http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html, and WEB_COMPONENTS sounds too generic anyway. There are other Web Components related APIs like custom dom elements and template .
--
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