Upcoming WHATNOT meeting on 2025-06-12

[cwilso]

What is the issue with the HTML Standard?

Today we held our weekly triage call (#11353) and I will post the meeting notes there in a bit. The next one is scheduled for June 5, 1am PDT. Note that this is 1 week later in the APAC-Europe friendly time.

People interested in attending the next call please respond here or reach out privately to @cwilso, or the editors. We will be tagging issues for the next call again using agenda+ in all WHATWG repositories across issues and pull requests and we would like to invite anyone that can contribute to join us.

[cwilso]

Thanks to all those who attending the meeting yesterday: Domenic, Keith, Olli, and Emilio.

The XML error behavior
XML error behavior for parseFromString() causing compat issues · Issue #11373 · whatwg/html · GitHub

Emilio: not necessarily opposed to doing the WebKit/Blink behavior, at least for non-SVG case, even though it's weird. Mozilla/spec behavior is simpler, and avoids half-broken pages, so would be kind of nice.

(Side discussion about Document vs. XMLDocument vs. HTMLDocument.)

Domenic: how bad would the compat issues be with going with the Gecko approach?

Emilio: the latest compat issue is a bizarre combination of site bugs, doesn't seem like it's indicative of a larger trend. We found one other, will try to link to it. It wasn't major, the site was usable.

Domenic: one reason I would prefer Gecko behavior is that there is no real XML parser spec so defining the part of the document to keep is hard.

Emilio: Would be curious to see if there's any historical archeology here. Blink behavior is inherited from WebKit. Any ideas where the WebKit behavior came from? Probably 20 years old.

Domenic: will pass along to the team.