Bug 96986 - [meta] Content reprojection for Shadow DOM
Summary: [meta] Content reprojection for Shadow DOM
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 96988 97151 99227 99228 99232 99552 99680 99750
Blocks: 63606 94082
  Show dependency tree / graph
 
Reported: 2012-09-18 00:24 PDT by Shinya Kawanaka
Modified: 2012-10-29 04:17 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shinya Kawanaka 2012-09-18 00:24:47 PDT 
We will make elements re-distributable in Shadow DOM.
This meta bug covers all issues related to it.
Comment 1 Shinya Kawanaka 2012-09-18 00:39:53 PDT 
In this series, we will make the following things available.

<host> ---- SR
  |                   |
  |- DIV (A)     |-DIV ---------------SR
  |- DIV (B)          |-<shadow> (D)        |-<content select="DIV"> (E)
                          |-DIV (C)

DIV (A) and DIV (B) are distributed to <shadow> (D) in the current spec.
In the coming spec, we will make it available to distribute (A) and (B) to (E) again. (This is called reprojection or redistribution)

This will improve the component-ability of elements much.
Comment 2 Shinya Kawanaka 2012-09-19 02:12:47 PDT 
When implementing content reprojection, we have to update both InsertionPoint, TreeWalker, etc. at once. 

It will be good to have some flag?
Comment 3 Dimitri Glazkov (Google) 2012-09-19 09:02:24 PDT 
(In reply to comment #2)
> It will be good to have some flag?

If we can avoid it, we should. If we can't, we could add a flag.
Comment 4 Hajime Morrita 2012-09-19 19:05:28 PDT 
Just for curious, that is the whole plan to make this happen?
Apparently Bug 96988 and Bug 97151 doesn't cover everything we need.
If there is some big picture for this,
it would be helpful for reviewing coming patches.
Comment 5 Dimitri Glazkov (Google) 2012-09-19 19:51:08 PDT 
(In reply to comment #4)
> Just for curious, that is the whole plan to make this happen?
> Apparently Bug 96988 and Bug 97151 doesn't cover everything we need.
> If there is some big picture for this,
> it would be helpful for reviewing coming patches.

+1 -- a plan sounds good.
Comment 6 Shinya Kawanaka 2012-09-25 21:19:07 PDT 
(In reply to comment #5)
> (In reply to comment #4)
> > Just for curious, that is the whole plan to make this happen?
> > Apparently Bug 96988 and Bug 97151 doesn't cover everything we need.
> > If there is some big picture for this,
> > it would be helpful for reviewing coming patches.
> 
> +1 -- a plan sounds good.

In my understandings, refactoring SelectorChecker and improving ComposedShadowTreeWalker will cover rendering things.
Comment 7 Shinya Kawanaka 2012-10-28 21:27:24 PDT 
all sub-bugs have been resolved. It's time to close this?
Comment 8 Hajime Morrita 2012-10-29 04:17:54 PDT 
(In reply to comment #7)
> all sub-bugs have been resolved. It's time to close this?
Good catch. Closing.