- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 09 Mar 2016 04:50:11 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Wednesday, 9 March 2016 12:51:09 UTC
I think I would be okay with this change. I initially pressed for "deep" since I thought we might have "path" meaning the path of the event without open shadow trees and "deep" could be a convention for APIs that include open shadow trees. However, as we consider more features and their integration with shadow trees, the more it seems like some of them might leak open shadow trees and not follow this "deep" naming. It does not really help that we still haven't established solid principles around this. Is anyone keeping track of APIs that leak open shadow trees in some way? --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/428#issuecomment-194281784
Received on Wednesday, 9 March 2016 12:51:09 UTC