No meeting in december Re: [web components] proposed meetings: 15 dec / 29 jan

[Chaals McCathie Nevile]

OK, just to formally close the loop we will not have a meeting in December.

cheers

On Mon, 16 Nov 2015 05:12:55 +0100, Hayato Ito  wrote:


Thank you, Ryosuke. I'm fine not to have a meeting in Dec.

Let me add a link to GitHub issue(s) for each item:


1. Clarify focus navigation


I think the following two GitHub issues are good starting points to know
the current status.
https://github.com/w3c/webcomponents/issues/103
https://github.com/w3c/webcomponents/issues/126


2. Clarify selection behavior (at least make it interoperable to JS)


https://github.com/w3c/webcomponents/issues/79
I think this is the hardest issue for us.


3. Decide on the style cascading order


https://github.com/w3c/webcomponents/issues/316
I think everyone can agree on Proposal 1, as I commented in the issue.


4. style inheritance


https://github.com/w3c/webcomponents/issues/314
I've already closed this issue. Please feel free to re-open the issue to
restart the discussion.


On Sat, Nov 14, 2015 at 1:31 AM Ryosuke Niwa  wrote:



> On Nov 13, 2015, at 8:08 AM, Anne van Kesteren   
wrote:

>
> On Fri, Nov 13, 2015 at 4:57 PM, Ryosuke Niwa  wrote:
>> What outstanding problems are you thinking of?
>
> Again, not I, but Hayato Ito raised these. I just happen to agree. He
> emailed this list on November 2:
>
>
https://lists.w3.org/Archives/Public/public-webapps/2015OctDec/0149.html

Of the four issues listed there:

> On Nov 1, 2015, at 7:52 PM, Hayato Ito  wrote:
>
> > 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'd like to resolve 3 and 4 ASAP since we're pretty close.  I don't  
think
we necessarily need an in-person meeting to do that though.  If  
anything,

it's probably more helpful to have discussion over mailing lists so that
each person can spend as much time as needed to understand / come up  
with

examples and proposals.

For 1, we had a rough consensus on how current focus model (in  
particular

focus ordering) should be changed to support shadow DOM during TPAC.
Namely, we would create a new tab index "scope" at both shadow roots as
well as slots, and follow the composed tree order for tab ordering.  I
think someone should document that first.

I just started working on 2 but I probably won't have a time to come up
with a proposal until mid December.


So if you guys can't make it, I don't think we necessarily need a shadow
DOM meeting in December.

- R. Niwa






--
Charles McCathie Nevile - web standards - CTO Office, Yandex
 cha...@yandex-team.ru - - - Find more at http://yandex.com

29 Jan? Re: [web components] proposed meetings: 15 dec / 29 jan

[Chaals McCathie Nevile]

Hi folks,

having canceled the proposed december meeting, and with a little less time  
pressure, this is a check that people are still interested in a face to  
face meeting for web components stuff - shadow DOM and custom elements  
both have some currently outstanding issues.


I changed the URL of the github page:

https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/29janWC.md

If you expect to attend, please add your name to that page directly by  
Pull Request, or let me know and I will do so. Ditto for agenda items.


Note that we are looking for a host still.

cheers


On Fri, 13 Nov 2015 11:32:06 +0100, Chaals McCathie Nevile  
 wrote:




https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/15decWC.md
https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/16janWC.md

Offers of hosting will be very gratefully received. We need a room for  
about 20 people, electricity, wifi, coffee/tea/snacks, lunch, and a  
speaker/mic setup for connecting remote participants.


And of course agenda…

cheers




--
Charles McCathie Nevile - web standards - CTO Office, Yandex
 cha...@yandex-team.ru - - - Find more at http://yandex.com

Re: [web components] proposed meetings: 15 dec / 29 jan

[Hayato Ito]

Thank you, Ryosuke. I'm fine not to have a meeting in Dec.

Let me add a link to GitHub issue(s) for each item:

> 1. Clarify focus navigation

I think the following two GitHub issues are good starting points to know
the current status.
https://github.com/w3c/webcomponents/issues/103
https://github.com/w3c/webcomponents/issues/126

> 2. Clarify selection behavior (at least make it interoperable to JS)

https://github.com/w3c/webcomponents/issues/79
I think this is the hardest issue for us.

> 3. Decide on the style cascading order

https://github.com/w3c/webcomponents/issues/316
I think everyone can agree on Proposal 1, as I commented in the issue.

> 4. style inheritance

https://github.com/w3c/webcomponents/issues/314
I've already closed this issue. Please feel free to re-open the issue to
restart the discussion.


On Sat, Nov 14, 2015 at 1:31 AM Ryosuke Niwa  wrote:

>
> > On Nov 13, 2015, at 8:08 AM, Anne van Kesteren  wrote:
> >
> > On Fri, Nov 13, 2015 at 4:57 PM, Ryosuke Niwa  wrote:
> >> What outstanding problems are you thinking of?
> >
> > Again, not I, but Hayato Ito raised these. I just happen to agree. He
> > emailed this list on November 2:
> >
> >
> https://lists.w3.org/Archives/Public/public-webapps/2015OctDec/0149.html
>
> Of the four issues listed there:
>
> > On Nov 1, 2015, at 7:52 PM, Hayato Ito  wrote:
> >
> > > 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'd like to resolve 3 and 4 ASAP since we're pretty close.  I don't think
> we necessarily need an in-person meeting to do that though.  If anything,
> it's probably more helpful to have discussion over mailing lists so that
> each person can spend as much time as needed to understand / come up with
> examples and proposals.
>
> For 1, we had a rough consensus on how current focus model (in particular
> focus ordering) should be changed to support shadow DOM during TPAC.
> Namely, we would create a new tab index "scope" at both shadow roots as
> well as slots, and follow the composed tree order for tab ordering.  I
> think someone should document that first.
>
> I just started working on 2 but I probably won't have a time to come up
> with a proposal until mid December.
>
>
> So if you guys can't make it, I don't think we necessarily need a shadow
> DOM meeting in December.
>
> - R. Niwa
>
>
>

[web components] proposed meetings: 15 dec / 29 jan

[Chaals McCathie Nevile]

Hi folks,

in the poll we ran, there were only about 10 responses, and the preference  
split was pretty even. I also forgot to make a place where people could  
provide their name :(


Our proposal is to look for a host on 15 December on the West Coast, for a  
meeting primarily focused on Shadow DOM, and another on 29 January in the  
Bay area for one around Custom Elements. The agenda can be adjusted to  
take account of people who are unable to travel for both of these, moving  
items from one to the other if necessary, since *many* but *not all*  
people are interested in both topics.


If people are seriously uncomfortable with this proposal, and want to  
argue for an alternative, please speak up - and if you're planning to  
attend either, please reply to this thread, privately to me, or add your  
name to the meeting pages with a Pull Request:


https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/15decWC.md
https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/16janWC.md

Offers of hosting will be very gratefully received. We need a room for  
about 20 people, electricity, wifi, coffee/tea/snacks, lunch, and a  
speaker/mic setup for connecting remote participants.


And of course agenda…

cheers

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
 cha...@yandex-team.ru - - - Find more at http://yandex.com

Re: [web components] proposed meetings: 15 dec / 29 jan

[Ryosuke Niwa]

> On Nov 13, 2015, at 8:08 AM, Anne van Kesteren  wrote:
> 
> On Fri, Nov 13, 2015 at 4:57 PM, Ryosuke Niwa  wrote:
>> What outstanding problems are you thinking of?
> 
> Again, not I, but Hayato Ito raised these. I just happen to agree. He
> emailed this list on November 2:
> 
>  https://lists.w3.org/Archives/Public/public-webapps/2015OctDec/0149.html

Of the four issues listed there:

> On Nov 1, 2015, at 7:52 PM, Hayato Ito  wrote:
> 
> > 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'd like to resolve 3 and 4 ASAP since we're pretty close.  I don't think we 
necessarily need an in-person meeting to do that though.  If anything, it's 
probably more helpful to have discussion over mailing lists so that each person 
can spend as much time as needed to understand / come up with examples and 
proposals.

For 1, we had a rough consensus on how current focus model (in particular focus 
ordering) should be changed to support shadow DOM during TPAC.  Namely, we 
would create a new tab index "scope" at both shadow roots as well as slots, and 
follow the composed tree order for tab ordering.  I think someone should 
document that first.

I just started working on 2 but I probably won't have a time to come up with a 
proposal until mid December.


So if you guys can't make it, I don't think we necessarily need a shadow DOM 
meeting in December.

- R. Niwa

Re: [web components] proposed meetings: 15 dec / 29 jan

[Ryosuke Niwa]

> On Nov 13, 2015, at 3:07 AM, Anne van Kesteren  wrote:
> 
> On Fri, Nov 13, 2015 at 11:32 AM, Chaals McCathie Nevile
>  wrote:
>> Our proposal is to look for a host on 15 December on the West Coast, for a
>> meeting primarily focused on Shadow DOM, and another on 29 January in the
>> Bay area for one around Custom Elements. The agenda can be adjusted to take
>> account of people who are unable to travel for both of these, moving items
>> from one to the other if necessary, since *many* but *not all* people are
>> interested in both topics.
> 
> As mentioned before, I and others from Mozilla not in the US are
> unlikely to make December 15. There's a big Mozilla event the entire
> week before and I doubt folks want to keep trucking. But given how far
> along Shadow DOM is perhaps attendance is not important. After all,
> Hayato Ito stressed in an earlier email that to make the meeting
> worthwhile we'd need some new proposals to address the quite hard
> outstanding problems and I haven't seen any of those thus far.

What outstanding problems are you thinking of?

- R. Niwa

Re: [web components] proposed meetings: 15 dec / 29 jan

[Anne van Kesteren]

On Fri, Nov 13, 2015 at 4:57 PM, Ryosuke Niwa  wrote:
> What outstanding problems are you thinking of?

Again, not I, but Hayato Ito raised these. I just happen to agree. He
emailed this list on November 2:

  https://lists.w3.org/Archives/Public/public-webapps/2015OctDec/0149.html


-- 
https://annevankesteren.nl/

Re: [web components] proposed meetings: 15 dec / 29 jan

[Anne van Kesteren]

On Fri, Nov 13, 2015 at 11:32 AM, Chaals McCathie Nevile
 wrote:
> Our proposal is to look for a host on 15 December on the West Coast, for a
> meeting primarily focused on Shadow DOM, and another on 29 January in the
> Bay area for one around Custom Elements. The agenda can be adjusted to take
> account of people who are unable to travel for both of these, moving items
> from one to the other if necessary, since *many* but *not all* people are
> interested in both topics.

As mentioned before, I and others from Mozilla not in the US are
unlikely to make December 15. There's a big Mozilla event the entire
week before and I doubt folks want to keep trucking. But given how far
along Shadow DOM is perhaps attendance is not important. After all,
Hayato Ito stressed in an earlier email that to make the meeting
worthwhile we'd need some new proposals to address the quite hard
outstanding problems and I haven't seen any of those thus far.


-- 
https://annevankesteren.nl/