Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2019 TPAC F2F #826

Closed
rniwa opened this issue Jul 29, 2019 · 38 comments
Closed

2019 TPAC F2F #826

rniwa opened this issue Jul 29, 2019 · 38 comments

Comments

@rniwa
Copy link
Contributor

@rniwa rniwa commented Jul 29, 2019

Thanks to @LJWatson and @hober, we have a room at TPAC on Tuesday, September 17th.

Minutes are available here: https://www.w3.org/2019/09/17-components-minutes.html

This issue tracks the agenda for this F2F.

Topics

@mfreed7

This comment has been minimized.

Copy link

@mfreed7 mfreed7 commented Jul 30, 2019

I would like to attend this meeting if possible - will signups happen here on this thread, or will this meeting get added to the TPAC registration?

Also, I think you meant Tuesday, Sept 17.

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Jul 30, 2019

Corrected the month.

@LJWatson / @hober : Would there be HTML listing for TPAC? Or should we sign up for WICG?

@LJWatson

This comment has been minimized.

Copy link

@LJWatson LJWatson commented Aug 20, 2019

The ARIA WG would welcome some time to:

  • Share progress on HTML role parity in ARIA 1.2
  • Discuss plans for ARIA 1.3 and a proposal to prioritise attribute parity

cc ARIA WG co-chairs @jnurthen and @joanmarie

@annevk

This comment has been minimized.

Copy link
Member

@annevk annevk commented Aug 20, 2019

Is it also possible to have that meeting on another day as it's not directly about web components? (To be clear, it's definitely a meeting worth having.) With regards to web components it might be good to discuss the various APIs around web components and ARIA.

@LJWatson

This comment has been minimized.

Copy link

@LJWatson LJWatson commented Aug 20, 2019

The effort to reach HTML role parity was prompted by Web Components, first raised here in #552, and continued in discussion at TPAC 2016.

@LJWatson

This comment has been minimized.

Copy link

@LJWatson LJWatson commented Aug 20, 2019

If time is limited on Tuesday, perhaps time could be found for it on the ARIA WG agenda on Monday though?

@jnurthen

This comment has been minimized.

Copy link
Member

@jnurthen jnurthen commented Aug 20, 2019

The ARIA working group is fine with either Monday or Tuesday.

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Aug 29, 2019

cc'ing more people for agenda building.

@dandclark @travisleithead @justinfagnani @diervo @caridy @muan @JanMiksovsky @tomalec @tkent-google @rakina

TPAC F2F is usually more focused on resolving issues with existing features and intersections with other WG's specifications; e.g. CSS and accessibility related features. If there are any topics you wish we made more progress, please let us know.

@jnurthen

This comment has been minimized.

Copy link
Member

@jnurthen jnurthen commented Sep 3, 2019

@LJWatson do you have a time for the meeting with ARIA. I am finalising our agenda.
We can do any time except Tuesday morning when we have other joint meetings scheduled.

@JanMiksovsky

This comment has been minimized.

Copy link

@JanMiksovsky JanMiksovsky commented Sep 3, 2019

Topics I’m interested in discussing include:

  • Checking in on ::part — any remaining issues to resolve?
  • Custom states
  • delegatesFocus

Also, could we spend some time discussing support for untrusted components? At the Spring 2019 F2F in Toronto, SalesForce indicated that they do a substantial amount of custom work to defend against security and stability concerns that arise when one org wants to use a component from a different org. It’s my understanding that Amazon has made a large investment in a proprietary component architecture because they don’t want to accept the risks that come with web components. I believe their requirements extend to protecting one internal team from incidental interference caused by components from other internal teams. I recall Apple raising questions about untrusted components back in 2015 or so, but I can’t remember the last time the topic’s been discussed.

@caridy

This comment has been minimized.

Copy link

@caridy caridy commented Sep 4, 2019

From our side, I will like to see progress on the following items (in order of importance):

  • scoped registries (not sure if the we have any progress here, @justinfagnani)
  • adopted stylesheets (we need to get on the same page to move this forward)
  • delegatesFocus (seems that we are pretty close on this one)
  • custom states (hopefully we can get some traction on this one, seems to be small enough)
  • aria properties (probably to be discussed on the accessibility forum instead)

Additionally, I will like to see few new avenues to be explored:

  • As @JanMiksovsky mentioned, untrusted components is by far the biggest, maybe we can just do a small presentation to highlight the current situation, and see if the group is open for explorations on this topic.
  • Stacking (modals, popups, etc, we continue having issues with the limitations imposed by the platform on this regards, maybe Iuri can put something together).
@LJWatson

This comment has been minimized.

Copy link

@LJWatson LJWatson commented Sep 4, 2019

@jnurthen

This comment has been minimized.

Copy link
Member

@jnurthen jnurthen commented Sep 4, 2019

@jnurthen could you find 30 minutes on the ARIA WG schedule on Monday perhaps? @annevk @domenic @rniwa, as people involved in the original discussion, would that work for you possibly?

Monday - 2pm? @LJWatson @annevk @domenic @rniwa

@rakina

This comment has been minimized.

Copy link
Contributor

@rakina rakina commented Sep 4, 2019

Recently added the custom element default focusability proposal: #834. Would like to discuss this in TPAC if possible!

@siusin

This comment has been minimized.

Copy link
Contributor

@siusin siusin commented Sep 6, 2019

For Remote Participants:

Tuesday, September 17, 2019
8:30 am | Japan Time (Tokyo, GMT+09:00) | 10 hrs

Join WebEx meeting
https://mit.webex.com/mit/j.php?MTID=m4a1eaf3e4e430bb1f37396a2367067f7
Meeting number: 647 038 848
Meeting password: visit this member-only archive or ask our co-chairs
Join from a video conferencing system or application
Dial 647038848@mit.webex.com
You can also dial 173.243.2.68 and enter your meeting number.

Join by phone
+1-617-324-0000 US Toll Number
Access code: 647 038 848
Mobile Auto Dial:+1-617-324-0000,,,647038848#

Add to your calendar

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 10, 2019

I've update the OP with the list of topics suggested so far. Let me know if I missed anything.

@rakina

This comment has been minimized.

Copy link
Contributor

@rakina rakina commented Sep 10, 2019

I've update the OP with the list of topics suggested so far. Let me know if I missed anything.

can you add custom element default focusability: #834?

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 10, 2019

I've update the OP with the list of topics suggested so far. Let me know if I missed anything.

can you add custom element default focusability: #834?

Oops, sorry. Done that.

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 10, 2019

@jnurthen @LJWatson : Monday 2pm ARIA WG time. Is that to discuss how ARIA / AOM interact with the shadow DOM / custom elements?

@dandclark

This comment has been minimized.

Copy link
Contributor

@dandclark dandclark commented Sep 10, 2019

I'm interested in talking about modules, particularly:

  • JSON modules: They've been built experimentally in Blink, any plans/concerns from other implementers?
  • CSS modules: discuss open issues, any blockers to adoption of scoped V1 implementation
@LJWatson

This comment has been minimized.

Copy link

@LJWatson LJWatson commented Sep 11, 2019

@rniwa asked:

: Monday 2pm ARIA WG time. Is that to discuss how ARIA / AOM interact with the shadow DOM / custom elements?>

The original discussion point from @jnurthen was HTML role parity for web components (from #552).

There are different conversations happening around AOM though, including use cases for immersive web, but I'm not sure how/where/when @alice, @cookiecrook and others are planning discussions.

@alice

This comment has been minimized.

Copy link
Contributor

@alice alice commented Sep 11, 2019

I would be happy to attend a session to discuss interactions between ARIA/AOM and Shadow DOM/Custom elements. Sounds like it's out of scope for the already scheduled ARIA WG session though.

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 11, 2019

Thanks for the clarifications. So let's schedule 30min ARIA for HTML role parity at 2pm.

@alice : do you want to discuss AOM in a different time slot? I don't think there is necessarily any blocker / concern in AOM pertaining to Shadow DOM / Custom Elements, is there?

@alice

This comment has been minimized.

Copy link
Contributor

@alice alice commented Sep 11, 2019

The thing I had in mind to discuss is the interaction between element reference IDL attributes and Shadow DOM boundaries.

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 12, 2019

The thing I had in mind to discuss is the interaction between element reference IDL attributes and Shadow DOM boundaries.

Alright, I added that as a topic. Any preference on when (as in time) to discuss that on Tuesday (e.g. after ARIA role discussion)?

@domenic

This comment has been minimized.

Copy link
Contributor

@domenic domenic commented Sep 12, 2019

I've added two more topics we'd like to discuss if possible:

  • Imperative shadow distribution API: discussion of what we've learned from the flagged implementation in Chromium, both on the implementation side and based on web developer feedback. Discussion of next steps toward formalizing and incorporating into the spec. @fergal will work on some brief slides to guide the discussion.

  • Mitigating flash of unstyled content with custom elements: discussion of the problem of FOUC with custom elements, especially as the world moves away from blocking scripts. We have some tentative sketches of what a solution could look like, but mostly want to open the discussion of the problem space. I will work on some slides.

@alice

This comment has been minimized.

Copy link
Contributor

@alice alice commented Sep 12, 2019

Any preference on when (as in time) to discuss that on Tuesday (e.g. after ARIA role discussion)?

Tuesday is looking pretty free for me so far, other than 11am. I'd like to sit in on the ARIA discussion anyway, so immediately following that would be convenient.

Thank you!

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 12, 2019

@cookiecrook : Does Tuesday 2:30pm also work for you (AOM discussion)?

@LJWatson

This comment has been minimized.

Copy link

@LJWatson LJWatson commented Sep 12, 2019

@rniwa

So let's schedule 30min ARIA for HTML role parity at 2pm.>

To confirm, this is on the Tuesday agenda?

@cookiecrook

This comment has been minimized.

Copy link

@cookiecrook cookiecrook commented Sep 12, 2019

@rniwa Yes

@smaug----

This comment has been minimized.

Copy link

@smaug---- smaug---- commented Sep 12, 2019

State propagation of lang, title and dir (are there other cases?)
whatwg/html#4906
whatwg/html#3821
whatwg/html#3699

In general we should go through the existing issues.

(in addition to those attribute states, we have had some rather tricky issues open for years, selection handling, session history etc.)

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 13, 2019

@smaug---- : Added that as a topic. I agree we should go through existing issues. I think we should probably allocate 2-3 hours of triaging session.

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 15, 2019

@lwatson / @hober : which room do we have on Tuesday & at what time are we starting?

@tomalec

This comment has been minimized.

Copy link
Contributor

@tomalec tomalec commented Sep 15, 2019

Could you also post the IRC channel that will be used for the meeting?

@smaug----

This comment has been minimized.

Copy link

@smaug---- smaug---- commented Sep 15, 2019

I guess we can use the same channel as last time, so, #components on irc.w3.org

@rniwa

This comment has been minimized.

Copy link
Contributor Author

@rniwa rniwa commented Sep 16, 2019

I talked to Tess in person, and the plan is to meet at 9am at Yoh, 3F.

@hober hober changed the title 2019 TPAC F2F Agenda 2019 TPAC F2F Sep 18, 2019
@hober

This comment has been minimized.

Copy link
Member

@hober hober commented Sep 18, 2019

Thank you, everyone, for a productive and interesting meeting yesterday. The minutes are here: https://www.w3.org/2019/09/17-components-minutes.html

@annevk

This comment has been minimized.

Copy link
Member

@annevk annevk commented Sep 19, 2019

The next meeting will likely be end of March 2020 in Paris.

@annevk annevk closed this Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.