| 08:28 | <zcorpan> | foolip: I think that makes sense |
| 08:50 | <zcorpan> | I'll run a new query for all of httparchive, with pi targets [a-zA-Z][a-zA-Z0-9-]* , excluding "xml" |
| 08:55 | <foolip> | zcorpan: if we define pseudo-attribute conformance properly (and it's implemented by validator.nu) do you think that changes the calculus for > vs ?> in serialization and conformance requirements? |
| 09:00 | <zcorpan> | foolip: I'm ok with > if the serializer omits ?. I suppose the lack of HTML parser-level parse error means some people will miss errors, but it's probably a small set of people anyway (who use an HTML parser in their pipeline but not validator.nu) |
| 09:00 | <foolip> | I've been looking at how to define conformance. I think it would be something analagous to "The value attribute, if specified and not empty, must have a value that is a valid time string." |
| 09:01 | <foolip> | zcorpan: could we report parse errors without actually parsing? |
| 09:03 | <zcorpan> | foolip: would need to step through new pseudo-attribute states in the tokenizer to get it right. It's overkill for just reporting errors from the parser |
| 09:37 | <zcorpan> | I proposed a change to the CSS of generated spec diffs. Which approach is more usable for screen reader users? See https://github.com/w3c/htmldiff-ui/issues/23 |
| 09:54 | <Julian Descottes> | Hi, I opened a PR for fetch to integrate with WebDriver BiDi at https://github.com/whatwg/fetch/pull/1860 . Anything I should do to make it move forward? (it's ok if it's just the normal process - things take time - just want to check if it wasn't missed or if I didn't forget to do something to make it actionable) |
| 11:15 | <zcorpan> | foolip: here are just the pi_target names and counts https://docs.google.com/spreadsheets/d/1mFzwvoixsIelVXgq3srm7aV2pjW8zcWpsH1wyp6Xfmo/edit?usp=sharing |
| 11:31 | <zcorpan> | Added a column for what chatgpt thinks the PI target is for |
| 12:29 | <Noam Rosenthal> | I researched a few of these, I can add notes with edit/suggest access |
| 13:07 | <zcorpan> | Noam Rosenthal: Done. |
| 13:09 | <zcorpan> | Noam Rosenthal: After checking a few URLs for xml-stylesheet, it seems the data includes JS resources even though the query tried to only include resources with type "html". e.g. https://instructor.go-red.co.uk/ has the matching PI in https://instructor.go-red.co.uk/portal/instructor/Login.aspx?_TSM_CombinedScripts_=True&v=ZaMfZ6yYhPPHZ1NeEf8j6-t902-6pHpn2MehV0eep-I1&_TSM_Bundles_=&cdn=False |
| 13:11 | <Noam Rosenthal> | This seems to be in a method initializeSVG so it probably creates a standalone SVG-XML doc on the fly |
| 13:13 | <zcorpan> | Noam Rosenthal: Right. Just something to keep in mind that not all matches are actually in HTML |
| 13:13 | <Noam Rosenthal> | Yea, <?lit$$ was in the lit js files... coincidentally that also blocked the chromium commit because chrome devtools uses lit :) |
| 13:35 | <foolip> | So there were 165k results, how many pages in HA in total? |
| 13:35 | <foolip> | Just wondering if it would be too noise to make more is these non-conforming because they don't use attribute syntax in the data part |
| 13:52 | <zcorpan> | foolip: 20727999 |
| 13:55 | <zcorpan> | @foolip:matrix.org: they are already non-conforming, should be fine |
| 13:58 | <foolip> | Cool, so about 0.8% |
| 13:58 | <foolip> | We can probably do what we think is the best long term then when it comes to conformance |
| 17:04 | <zcorpan> | foolip: 7,161 pages when excluding <?php. And some of those are still PHP |
| 18:03 | <zcorpan> | foolip: also I see 55,733 pages with PIs. The 165k rows is the number of PIs, not pages |
| 19:28 | <foolip> | Great, so at least we won't be adding red squiggles to lots of existing content |
| 19:28 | <foolip> | As you say, it was already non-conforming, so I guess my concern didn't make sense to begin with |
| 21:34 | <jmdyck> | https://html.spec.whatwg.org/#concept-optgroup-label has the phrase "excluding any that are descendants of descendants of the legend", and that "desc. of desc." seems odd. Note that it fails to exclude children of the legend (because, while they're descendants of the legend, they aren't descendants of descendants of the legend), but it seems like you do want to exclude them. |