Re: [webcomponents] isEncapsulated naming (#107)

Thanks for the feedback. I appreciate it.
I like the bikeshed. :)

I thought the same thing, like a 'event.xxxShadowHost', though I don't remember 'XXX'.

However, I abandoned it because I thought that it might impress developers that event is dispatched to only the shadow host (+ ancestor chain in the current node tree, of course), excluding the ancestor nodes of the shadow host. Am I worrying too much?

In addition to that, `includes` should be used for event.path, IMO.
If it is used as the attributes of the event, that might be weird.

`event.includesShadowHostInPath` might be better, but it is too long. :(

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/107#issuecomment-111024273

Received on Thursday, 11 June 2015 07:25:12 UTC