Re: [css-houdini-drafts] [css-paint-api] should registered paint names be somehow limited to shadow trees they are registered in?

Hmm, also scoping doesn't really work with the worklet system, you 
just import scripts into the worklet and they define the painters any 
part of the page can use. This is the same as global element names, 
CSS display types, or the urls to the image resources the custom 
element might use.

`js
window.paintWorklet.import("painter.js")
`

I'm not sure how to make that work for ShadowRoot, you'd need to 
somehow associate specific names in the worklet with specific custom 
element names or shadow roots. Per ShadowRoot or Element worklets 
would be too expensive. So we'd have to redesign the API somehow, I 
guess registerPainter in the Worklet itself could limit it to specific
 element names?

I'm not sure that complexity is much better than just prefixing your 
layouts or painters with the element name, just like you'd scope the 
urls for images, or prefix the custom element name itself.

-- 
GitHub Notification of comment by esprehn
Please view or discuss this issue at 
https://github.com/w3c/css-houdini-drafts/issues/223#issuecomment-227239116
 using your GitHub account

Received on Monday, 20 June 2016 19:09:21 UTC