| 10:11 | <csarven> | In say the references section of an article, <cite><a href></a></cite> feels intuitive to me for some reason, but I do find <a href><cite></cite></a> perhaps more accurate. The former cites the link, the latter links to the citation.Could one pattern be more accurate in a certain context, e.g., in the body of an article or references section or elsewhere. Anyone have thoughts on this or can point me to some discussion? |
| 11:22 | <annevk> | Luca Casonato: any chance you can tackle https://github.com/whatwg/html/issues/6768? |
| 11:59 | <Luca Casonato> | Luca Casonato: any chance you can tackle https://github.com/whatwg/html/issues/6768? sure: https://github.com/whatwg/html/pull/10327 do you know if there is implementer interest from chromium or gecko? considering safari already implements this behaviour, can i count that as implementer interest? if we have two interested implementers i can write some tests |
| 12:09 | <Luca Casonato> | Also, still awaiting reviews for: (and more responses on implementer interest) |
| 12:57 | <annevk> | Luca Casonato: yeah, given that web developers seem to prefer it and WebKit already does it, that seems fine |
| 13:00 | <annevk> | Luca Casonato: I think WebKit is already interested in async iterable for ReadableStream (but not yet implemented iirc) so seems fine to carry that over to the Web IDL version |
| 13:00 | <annevk> | Luca Casonato: review is prolly best done by Mattias Buelens and Domenic |
| 13:02 | <Luca Casonato> | Luca Casonato: I think WebKit is already interested in async iterable for ReadableStream (but not yet implemented iirc) so seems fine to carry that over to the Web IDL version ReadableStream implementing async iterable, but right now this is just a spec refactor - it's for being able to pass async iterables to web APIs (initially refactoring ReadableStream.from), but then in the future also https://github.com/whatwg/fetch/issues/1291 |
| 13:03 | <Luca Casonato> | The "let an interface implement async iterable" is already in webidl - there was previously just not the reverse ("let a web api take an async iterable as an argument" |
| 13:11 | <annevk> | Luca Casonato: fair, but still good. I suppose I should double check for the Fetch change, but I don't foresee any issue there either. |
| 16:39 | <annevk> | https://github.com/whatwg/html/issues/4562 is very reminiscent of early "let's fix the URL parser" discussions, and not in a good way. Geez. |
| 16:54 | <sideshowbarker> | I can't see that jrlevine is actually contributing anything constructive at all there, and definitely not responding to any of the specific questions for which feedback was requested. And he's being outright insulting |
| 18:21 | <Meghan Denny> | I see the former as more accurate since the citation might include other text as well, not just the link and link text. eg picture is what im thinking of |
| 23:20 | <smaug> | Btw, CSS/WHATWG meeting overlaps PointerEvents meeting |
| 23:30 | <Alan Stearns> | smaug: does the PointerEvents meeting have a scheduled time we should avoid? |
| 23:30 | <smaug> | Alan Stearns: https://www.w3.org/groups/wg/pointer-events/calendar/ |
| 23:36 | <smaug> | was the plan for CSS/WHATWG meeting to be also bi-weekly? If so, could it be on those weeks when there isn't PEWG? |
| 23:41 | <Alan Stearns> | No plan of record yet. I think once a month might be sufficient. We can definitely schedule whatever it ends up being to avoid PEWG conflicts |