Summary: | ShadowElement::m_shadowParent should be removed | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Hajime Morrita <morrita> | ||||
Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | dglazkov, dominicc, rolandsteiner | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Bug Depends on: | 48698 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Hajime Morrita
2011-01-17 00:42:34 PST
Created attachment 79556 [details]
Patch
Hi Dimitri, could you take a look? I just removed an unused variable. Tests passed. Comment on attachment 79556 [details]
Patch
OK. Do we need to ref the parent? That's the only side-effect of this change I can see.
Hi Eric, thank you for taking a look! I'll land this soon. (In reply to comment #3) > (From update of attachment 79556 [details]) > OK. Do we need to ref the parent? That's the only side-effect of this change I can see. No, the shadow root belongs the host(parent), and the host has normal lifecycle as usual DOM node. Committed r76221: <http://trac.webkit.org/changeset/76221> For what it's worth, we should remove ShadowElement entirely. Its purpose is very limited already, and it'll become completely useless once we convert all elements that rely on it to new shadow DOM. (In reply to comment #6) > For what it's worth, we should remove ShadowElement entirely. Its purpose is very limited already, and it'll become completely useless once we convert all elements that rely on it to new shadow DOM. Yes. I think we should do it after shadow migration is finished. |