> 1. Clarify focus navigation > 2. Clarify selection behavior (at least make it interoperable to JS) > 3. Decide on the style cascading order > 4. style inheritance (https://github.com/w3c/webcomponents/issues/314) I'm happy to have the mentioned topics about Shadow DOM on the f2f if and only if: - We have well-defined one-or-more proposals other than the current spec - We've discussed the pros and cons of each proposal (and the current spec) well - However, we can not reach the consensus. Unless a well-defined proposal before the meeting, I'm afraid it would be difficult to have a consensus in the meeting. Topic 1) I can see one proposal about this topic: https://github.com/w3c/webcomponents/issues/126. This proposal doesn't replace the current behavior. It just adds the new feature to current behavior. Topic 2) This issue has been an unresolved problem for years. There is no proposal at all. Topic 3) This is the summary I've written: https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Shadow-DOM-Cascade-Order-in-v1.md Topic 4) There is no well-defined proposal other than the current spec. It wold be nice to make the situation clear before the meeting so that we don't have additional topics other than Custom Elements on f2f meetings. On Thu, Oct 29, 2015 at 3:07 PM Ryosuke Niwa <rniwa@apple.com> wrote: > > > > On Oct 29, 2015, at 9:47 AM, Chris Wilson <cwilso@google.com> wrote: > > > > Or host in Seattle. :) > > > > On Thu, Oct 29, 2015 at 9:20 AM, Travis Leithead < > travis.leithead@microsoft.com> wrote: > >> I would prefer a late January date so as to allow me to arrange travel. > Otherwise, I’m happy to attend remotely anytime. > > I'm okay with either option with a slight preference on having it earlier > since we didn't have much time discussing custom elements at TPAC. > > I would like to resolve the following issues for shadow DOM: > 1. Clarify focus navigation > 2. Clarify selection behavior (at least make it interoperable to JS) > 3. Decide on the style cascading order > > And the following issues for custom elements: > 4. Construction model. Do we do sync / almost-sync / dance? > 5. Do we support upgrading? If we do, how? > > Any other issues? > > - R. Niwa > > >
Received on Monday, 2 November 2015 03:52:57 UTC