| 05:46 | <vrafaeli> | Hi. I've already touch this topic few months ago, but what do you think about adding a feature that will add link semantics to custom elements, or at least to tr? Because I saw a lot of need for the table row to behave like a link and you cannot wrap it with an a element. |
| 05:47 | <vrafaeli> | Yea, actually this is what came to my mind https://github.com/whatwg/html/issues/6223 |
| 06:57 | <annevk> | vrafaeli: if there's no issue for link semantics in WICG/webcomponents it seems reasonable to open one. It won't help you with tr though. |
| 07:38 | <Domenic> | Link "semantics" are already possible with ariaRole |
| 07:39 | <Domenic> | It sounds like the desire is more for link behavior |
| 07:39 | <Domenic> | You can do that with <tr is="my-link" data-href="my-url"> |
| 07:39 | <Domenic> | Where my-link is a web component you write |
| 08:09 | <annevk> | Domenic: how do you get right-click semantics? |
| 08:09 | <annevk> | Domenic: a role is just conveying something to AT, nothing more, it's not the same |
| 08:10 | <Domenic> | I would call those right click behaviors, but yeah, fair point that you don't get them. |
| 08:11 | <annevk> | I think it's a semantic as what a UA chooses to offer for links is up to them and it might also vary wildly across platforms |
| 08:19 | <vrafaeli> | What is AT? |
| 15:00 | <Alan Stearns> | Assistive Technology |
| 18:25 | <Panos Astithas> | Panos Astithas: WHATNOT still conflicts with Interop |
| 21:27 | <vrafaeli> | annevk: What exactly are the challenges of implementing (adding to spec) href for <tr>? |