WHATWG on 2021-08-16

05:11	<hsivonen>	Regarding the `meta` prescan discussion from mid-July, I filed https://github.com/whatwg/html/issues/6962
07:51	<sideshowbarker>	annevk: is the answer at https://stackoverflow.com/questions/68793536/why-cant-i-use-a-wildcard-on-access-control-allow-headers-when-allow-credenti/68799055#68799055 a correct reading of that note in the spec?
07:53	<sideshowbarker>	that is, responses that include credentials can’t have `Access-Control-Allow-Headers: *` but must instead explicitly list all the allowed header names?
07:54	<sideshowbarker>	(or more precisely, in responses that include credentials, the `` in the `Access-Control-Allow-Headers` value is interpreted by browsers as the literal header name `` — not as the wildcard meaning “any header name”)
11:38	<annevk>	sideshowbarker: yeah
13:02	<hsivonen>	html5lib-tests expect `<!DOCTYPE>` to have `null` name. See https://github.com/validator/htmlparser/issues/35 . Yet, per https://dom.spec.whatwg.org/#documenttype , the name isn't nullable in the DOM, and is `""` rather than `null` in Chrome. Is the difference between `null` and `""` visible via the Web? Should the spec and test suite change instead of implementations?
13:03	<hsivonen>	(Context, trying to merge https://github.com/validator/htmlparser/commit/3be25a0e44adda338c99bcc85ae9b6167522bc75 to Gecko and wrote a WPT expecting `null`.)
13:34	<Sam Sneddon [:gsnedders]>	html5lib-tests expect `<!DOCTYPE>` to have `null` name. See https://github.com/validator/htmlparser/issues/35 . Yet, per https://dom.spec.whatwg.org/#documenttype , the name isn't nullable in the DOM, and is `""` rather than `null` in Chrome. Is the difference between `null` and `""` visible via the Web? Should the spec and test suite change instead of implementations? DOCTYPE tokens have a name, a public identifier, a system identifier, and a force-quirks flag. When a DOCTYPE token is created, its name, public identifier, and system identifier must be marked as missing (which is a distinct state from the empty string), and the force-quirks flag must be set to off (its other state is on). That said, I don't think anything (even parse errors) differ between null and "" for the name
13:36	<Sam Sneddon [:gsnedders]>	(for public identifiers and system identifiers it can be observed if you can observe parse errors, and in certain combinations by quirks mode activation)
13:37	<Sam Sneddon [:gsnedders]>	there's some kinda broad questions about how useful/accurate the tokeniser tests are, given for many implementations it's not possible to run the tokeniser in isolation
14:09	<zcorpan>	"Each Entity must: identify individuals who are authorized to participate in each Workstream, " - how do I do this?
14:32	<zcorpan>	Also can I just invite colleagues to the whatwg github org?
14:39	<Domenic>	Using the per-entity GitHub org
14:39	<Domenic>	Also can I just invite colleagues to the whatwg github org? Yeah historically we've used org membership as just "do you want a cool WHATWG badge on your profile" so anyone can join.
14:41	<zcorpan>	Domenic: so members of bocoup github org are allowed to participate in whatwg workstreams?
14:42	<Domenic>	Yes, since you set that as the org in https://github.com/whatwg/participant-data/blob/8a6e5999042588478cadb24c8e0480accc7c9b9a/entities.json#L189
14:43	<zcorpan>	aha, thanks. I'll check if we should use a dedicated org for standards stuff
15:31	<zcorpan>	hsivonen: I wonder if it's feasible to kill <noscript> and always parse as "scripting enabled"
15:47	<Ms2ger 💉💉>	What's a workstream?
15:49	<Luca Casonato>	"Workstream" means a unified technical development effort (in most cases developing a single Living Standard, more than one only if inextricably bound together). Workstreams and Contributions are publicly visible.
15:49	<Luca Casonato>	From https://whatwg.org/workstream-policy#definitions
15:54	<Ms2ger 💉💉>	So a kind of mini-WG?
15:54	<zcorpan>	Domenic: https://github.com/whatwg/infra/commit/cd60f9e3b54e915d4b86b4e09bda6d6ba6d4eb08#diff-9f2a5a182d15704e72509db6ba7bbb4e246b193e1775be20d70f8e96de33d990R948 can't start be equal to 0?
15:56	<Luca Casonato>	So a kind of mini-WG? WHATWG is in itself a working group, so having more working groups inside that working group would be confusing. So indeed, its comparable to a working group in W3C for example, except more "low overhead".
15:58	<Ms2ger 💉💉>	Back in my day, we didn't have any of this stuff :)
15:59	<zcorpan>	An Entity can participate in only some Workstreams, so I guess it's a way to limit IP concerns
16:16	<Domenic>	Domenic: https://github.com/whatwg/infra/commit/cd60f9e3b54e915d4b86b4e09bda6d6ba6d4eb08#diff-9f2a5a182d15704e72509db6ba7bbb4e246b193e1775be20d70f8e96de33d990R948 can't start be equal to 0? Oof, good catch, thank you.
16:17	<Domenic>	Hmm and length being 0 would be useful too, I think that must have been part of what annevk meant.