RESOLVED WONTFIX 95663
[Shadow DOM] <content> should allow being turned off separately 
https://bugs.webkit.org/show_bug.cgi?id=95663
Summary [Shadow DOM] <content> should allow being turned off separately
Hajime Morrita
Reported 2012-09-02 21:36:24 PDT
Since the <content> behavior is in flux, we need to have a flag to turn this off for a while.
Attachments
Patch (19.14 KB, patch)
2012-09-03 00:40 PDT, Hajime Morrita 		no flags
DetailsFormatted DiffDiff
Patch (20.50 KB, patch)
2012-09-03 03:29 PDT, Hajime Morrita 		dglazkov: review-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Hajime Morrita
Comment 1 2012-09-03 00:40:34 PDT
Created attachment 161870 [details] Patch
WebKit Review Bot
Comment 2 2012-09-03 00:43:10 PDT
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Hajime Morrita
Comment 3 2012-09-03 03:29:06 PDT
Created attachment 161893 [details] Patch
Hajime Morrita
Comment 4 2012-09-05 02:01:38 PDT
Chromium will enable this as a part of Shadow DOM. closing.
Dimitri Glazkov (Google)
Comment 5 2012-09-06 18:51:44 PDT
Comment on attachment 161893 [details] Patch We probably won't be using this.
Note You need to log in before you can comment on or make changes to this bug.