Changing web standards - HTTP 203

Something a bit different for HTTP 203: Jake & Surma make a change to a web standard. Includes how to read specs, and how to write web platform tests.

01:37 There's a problem with IndexedDB.
07:07 How do we start adding a feature to the web?
08:24 How to find the right spec.
10:15 The structure of a web spec.
13:26 Proposing a new feature.
16:29 THE WORK BEGINS.
16:55 Test-driven standards development.
37:54 Changing the spec.
55:07 Revisiting the tests.
58:15 Opening PRs.

Links:

[RafaelCouto]

This was the most precious class about the web platform documentation I've ever seem.
I've been afraid to be a part of it and to make those kind of small contributions because of all the things you cleared here. Thx a lot!

[amr]

That was extremely fun to watch. Thanks for the episode!

[hypersonic]

This was *immensely* useful, thanks so much for the walkthrough. Would be also interesting to see the process for proposing a completely new spec.

[raqbit]

Oh man, that SuperCharged intro was fun!. Props to the editors for actually including that :)

[brandonbodine]

Nice, I always wondered how some web standards get updated. Going through all the steps in the process was really insightful. Thank you!

[Lifelightning]

Please do more code-writing episodes, this is invaluable pair programming dialogue!

[wmhilton-old]

This was SO GOOD! I feel empowered to start editing specs now!

[marcpicaud]

Loved this one, thank you ! Please do more of these, it's fun to watch, and full of valuable learnings.

[ColinRichardson]

Two line changed turned into 17 lines plus a discussion on how you copied/pasted to keep consistency, and found that what you copied was inconsistent.
Story of my life.

[hnasr]

IndexedDB api is so weird. Made a whole video about it

[teamgartz-motorsports]

Great video!

I believe you have a fair point. You could also remove the success callback from the request when the callback is executed, so it will be executed only once. That can use scope or a function proxy if you don’t have access to the request.

But having access to the request makes it much easier.

[nicolasparada]

This is very good. Thanks Jake ... and Surma :)

[samuelgozi]

Thank you very much for this episode, I've wanted to how its done for a while!

[jhpratt]

Jake — Have you seen the "indent on paste" extension for VS Code? Super useful, and it doesn't seem like you have it installed.

[alaaradwan]

I do love what are you doing
Really funny
Thanks a lot ✌

[Bigjunior]

How about a video how this feature get's implemented directly in Chrome?

[victornpb]

Oh, I was just thinking about DMing Surma on twitter asking for help to write a proposal, this was last week I haven't got to it, so ty for reading my mind and fulling my request Jake.

[delulu]

From what I learned about TDD, the tests should be more explicit and sequential? Like the one you refer to

[Idolaughtmyheadoff]

Thanks a lot, It was really cool episode)

[MrZyclops]

Great Episode, I had no idea that the general public could make suggestions and changes to the specifications. Couple of questions:


1. Suggestions without Tests/Implementation


I'd like to suggest to add the equivalent of flex-shrink to CSS grid, but I think I've only got the skill level to demonstrate exactly why it's needed and what the use cases are and why CSS grid is lacking in areas compared to flexbox. I can create two implementations of the issue (a flexbox implementation and a css grid implementation) but I don't think I'm expert enough to actually implement or write the spec. If it's well written enough, do you think it would get considered?


Especially considering this would be a major change to the CSS grid specification


2. Suggesting Entirely New APIs
Is there anywhere we can write up and put forward entirely new APIs or a working group where we can put these ideas forward