- From: Caridy Patiño <notifications@github.com>
- Date: Mon, 19 Nov 2018 14:00:44 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 November 2018 22:01:09 UTC
> We need to have something where we are not trying to run JS before something else could be. This approach, which is fine for now, will lead to a point where the atoms lose the race. We need a solution that never hits that situation. @AutomatedTester yes, that's why we are supportive of such API, so we don't have to play the race game. > @diervo what does a selector look like for you? Do you need to explicitly specify each element that has a shadow root along the way? Yes, you have to get inside the shadow at every level, unless you rely on our high level API to access page segments as @diervo described above. We don't want arbitrary queries to return stuff from inside a shadow. We did entertained the idea of using something equivalent to ::shadow selector (IIRC), but that might confuse folks that they might be able to use the same selector in production code, which will not work. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/771#issuecomment-440057083
Received on Monday, 19 November 2018 22:01:09 UTC