Bug 58584

Summary: Expose shadowPseudoId property to script
Product: WebKit Reporter: Dimitri Glazkov (Google) <dglazkov>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: cmarcelo, dominicc, rolandsteiner
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Bug Depends on: 63604, 63657    
Bug Blocks: 63606    
Attachments:
Description Flags
proposed patch dglazkov: review-

Description Dimitri Glazkov (Google) 2011-04-14 15:36:06 PDT 
Authors should be able to read and write the shadowPseudoId property on an element.
Comment 1 Dominic Cooney 2011-04-19 19:56:32 PDT 
Should that be a reflected attribute, or just a property?
Comment 2 Dimitri Glazkov (Google) 2011-04-20 09:54:33 PDT 
(In reply to comment #1)
> Should that be a reflected attribute, or just a property?

Reflected attribute, I think.
Comment 3 Philippe Normand 2011-05-03 02:19:06 PDT 
Created attachment 92055 [details]
proposed patch
Comment 4 Dimitri Glazkov (Google) 2011-05-03 06:39:21 PDT 
Comment on attachment 92055 [details]
proposed patch

This would actually expose this as a public API on all DOM elements. We're not quite ready for this yet.
Comment 5 Dimitri Glazkov (Google) 2011-05-03 06:46:52 PDT 
As an alternative, you could expose a layoutTestController.pseudoShadowId(node) method, which queries the node and returns its pseudoShadowId.
Comment 6 Philippe Normand 2011-05-03 09:32:03 PDT 
Ok then, I guess the new patch should be in a separate bug?
Comment 7 Dimitri Glazkov (Google) 2011-05-03 09:45:58 PDT 
(In reply to comment #6)
> Ok then, I guess the new patch should be in a separate bug?

Yep, that should go under testing (blocking bug 59823).
Comment 8 Ami Fischman 2011-05-04 16:24:09 PDT 
For the record, the new bug tracking LayoutTestController's access to pseudoShadowId is bug 60034.
Comment 9 Dimitri Glazkov (Google) 2012-01-06 12:58:27 PST 
This is probably not going to be exposed directly like that. We'll file a new bug if we need it.