-
Notifications
You must be signed in to change notification settings - Fork 0
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
Web Components & ARIA #30
Comments
Thank you for proposing a session! You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions. Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting. |
Minutes from TPAC breakout session discussion: Sanket Joshi 12:10 PM — Zakim sees alice on the speaker queue 12:11 PM Sanket Joshi Michael_Warren: Someone said id ref different than other ARIA references. How different are the implementations? 12:11 PM dandclark: reftarget as proposed is not limited to ARIA 12:11 PM ...: supports all id based lookups 12:12 PM masonf: string based ones could technically be adapted too 12:12 PM rniwa: are we adjusting svg use too? 12:12 PM lea: uses href, not id 12:13 PM rniwa: resolved to change semantics, does use id for things with that SVG tree 12:13 PM dandclark: not adjusted those 12:13 PM rniwa: may need to review where id lookup is done 12:13 PM q? 12:13 PM — Zakim sees alice on the speaker queue 12:13 PM q? 12:13 PM — Zakim sees alice on the speaker queue 12:14 PM ack alice 12:14 PM Bridge daemon alice, you wanted to go back to the question if we have tiem 12:14 PM — Zakim sees no one on the speaker queue 12:14 PM Sanket Joshi alice: RE form question: Not sure about issues from leaking, but tells info about host, which means it can 'act' as an element you are targeting 12:14 PM ⇐ ethanjv quit (~ethanjv@9d40a032.publics.cloak) 12:14 PM Sanket Joshi keith: what about .form today on an element? 12:14 PM ...: that's undefined, right? 12:15 PM dandclark: yeah, might be compat since it returns null today and now invalid ref would cause it to return the host 12:16 PM keith: Restating... .form returns null if element not form participant, but if reftarget always fallbacks to host, then .form will always fallback to the host element and look like a form participant 12:17 PM dandclark: Maybe a good principal is that reftarget won't change property reflections or other internal associations 12:17 PM q+ 12:17 PM — Zakim sees xiaochengh on the speaker queue 12:17 PM Sanket Joshi ...: For aria properties, would just change those internal associations, but not the property reflections 12:18 PM keith: No way to use form property on custom element, right? 12:18 PM ⇐ kschmi and justinf quit 12:18 PM ack xiaochengh 12:18 PM — Zakim sees no one on the speaker queue 12:19 PM Sanket Joshi xiaochengh: Maybe shouldn't push reftargetmap to level 2? 12:19 PM lea: That's a lot more complex. Forwarding everything to one element is simpler and addresses a lot of use cases. 12:19 PM xiaochengh: Risky. Ex: How do we address form? 12:20 PM ⇐ jarhar, masonf, jocelyntran3, alisonmaher, Di and xiaochengh quit 12:20 PM Sanket Joshi masonf: Maybe we try to address all properties first and strive for reftarget only in level 1. |
Session description
Session to discuss ARIA and web components:
https://github.com/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.md
Session goal
Concrete proposal for ARIA across shadow trees
Additional session chairs (Optional)
No response
Who can attend
Anyone may attend (Default)
IRC channel (Optional)
#webcomponents
Other sessions where we should avoid scheduling conflicts (Optional)
#26, #27, #28, #29
Instructions for meeting planners (Optional)
No response
Agenda for the meeting.
No response
Links to calendar
Meeting materials
The text was updated successfully, but these errors were encountered: