WHATWG
2021-06-28
plaintext logs
prev next
source on github
06:50
<Ms2ger>
Why?
08:17
<Ms2ger>
hsivonen: any reason on your side not to merge https://github.com/html5lib/html5lib-tests/pull/136 ?
12:39
<Jake Archibald>
  1. See a line in the HTML spec you feel unsure about
  2. Do a bunch of thinking & testing to conclude that the spec is wrong in Case X
  3. Go to add a note to the spec, and find an HTML comment saying "btw this doesn't work with Case X"
13:50
<Domenic>
Yeah, some HTML comments in the spec should definitely be visible...
13:55
<Ms2ger>
But there's no more todo's in the spec, Hixie fixed them all for Last Call
14:19
<Jake Archibald>
hah
16:41
<Domenic>
sideshowbarker: I reorganized and updated https://wiki.whatwg.org/wiki/Fork_tracking in case it helps with the efforts to clean things up on the W3C side
16:55
<sideshowbarker>
thanks!
19:41
<Luca Casonato>

Is there a set process to follow for new web platform proposals? From what I have gathered through looking at other relatively new specs, something like this?

  1. Create an explainer/proposal stating the problem, prior art, possible solutions
  2. Gather implementer and user interest (just open issues on crbug, mozilla/standards-positions, webkit mailing list?)
  3. Gather and incorporate feedback into proposal
  4. Write proper spec
  5. Implement in engines
  6. Ship
20:19
<Domenic>
Trying to make HTML a tiny bit less painful to contribute to: https://github.com/whatwg/html/pull/6810
20:21
<Domenic>

Is there a set process to follow for new web platform proposals? From what I have gathered through looking at other relatively new specs, something like this?

  1. Create an explainer/proposal stating the problem, prior art, possible solutions
  2. Gather implementer and user interest (just open issues on crbug, mozilla/standards-positions, webkit mailing list?)
  3. Gather and incorporate feedback into proposal
  4. Write proper spec
  5. Implement in engines
  6. Ship
This is about right. See also https://whatwg.org/faq#adding-new-features . Step 2 is very tricky and I'm not sure the specific venues you suggest will work that great. Step 4 and 5 often take place in parallel and step 3 happens continuously of course.
20:23
<Domenic>
https://www.chromium.org/blink/launching-features "new feature incubations" section gives some insight into how we expect Chromium engineers to do such work
20:37
<Luca Casonato>
Domenic: Thanks, that's very useful info. So according to that, now that I have an explainer with motivation and use cases, I go find a standards venue to incubate the proposal? I guess that would be WICG? Or is there a WHATWG version of WICG?
20:47
<Domenic>
Yeah, WICG is good in general. If it's a modification to or natural extension of an existing spec (e.g. a WHATWG spec) then opening an issue on that spec to involve that community would be ideal.
20:48
<Luca Casonato>
Cool - I'll look into WICG then. Thanks again!
20:53
<Andreu Botella (he/they)>
Luca Casonato: If you're talking about https://github.com/lucacasonato/proposal-binary-encoding, that's probably small enough that a PR to the HTML standard would do
20:53
<Andreu Botella (he/they)>
Though you should look at https://github.com/bakkot/proposal-arraybuffer-base64, which was created a couple days ago
20:54
<Luca Casonato>
Oh interesting! Thanks for the link :-)