If you want to get into web platform development and push features into browsers, I wrote a few words that I hope can be useful: https://blog.yoav.ws/posts/so_you_want_to_push_a_web_platform_feature/

Delete-Cookie header?

https://lists.w3.org/Archives/Public/ietf-http-wg/2024OctDec/0147.html

I'm excited that we're finally getting a customisable <select> on the web. However, there's one detail of it I'm really not sure about, and I'd like to hear your thoughts.

Have your say before it's too late 😀

https://jakearchibald.com/2024/how-should-selectedoption-work/

@scott it's feasible, but would require a bunch of work and a different loading scheme - an opt in would tell browsers to load the images head first (to get byte ranges of the different resolutions) and only then load the required rest

@scott https://blog.yoav.ws/posts/responsive_image_container/ from almost 11 years ago is still relevant, and I don't think JXL is it..

@scott I hear you on the authoring woes (and apologies for failing to make it better), but nothing about jxl enables the "stop when you have enough" bit

@scott how does jxl do that?

@meduz I'd love to better understand scenarios you're seeing for more than a single original language (other than content aggregators, I guess), or when would users prefer a translation over the original if they can read it

(BTW, this is what I meant when I wrote up https://blog.yoav.ws/posts/web_platform_change_you_do_not_like/ over a year ago)

I think language negotiation on the web can be both better *and* more private. So I wrote up a few words https://blog.yoav.ws/posts/improving_language_negotiation/

Blink: Intent to Prototype: Dynamic import maps https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSJrxQj19LattoOyE3Af5dn%3D50UD9ecpHZWjVZ5-GrMr9w%40mail.gmail.com

WebDriver BiDi production-ready in Firefox, Chrome and Puppeteer

https://developer.chrome.com/blog/firefox-support-in-puppeteer-with-webdriver-bidi?hl=en

Next step - a prototype Chromium CL and web platform tests (most probably a “translation” of the spec examples into test cases) as well as sending out requests for positions on WebKit and Mozilla

For the last week or so i've been working on an HTML PR to enable multiple import maps per document: https://github.com/whatwg/html/pull/10528

Now that the PR iteration process feels like we’re almost there , I think it’s time to start prototyping and see that it all actually works in practice. So I created a mapping from the relevant spec concepts to Chromium code: https://docs.google.com/document/d/1O2OlzcSVWF-8mmXr_Nz0ryz5CUiETyzPydOViE_9WRs/edit

Just to share a little bit of my web platform feature process..

Following some user-visible breakage related to importmaps (https://x.com/thommaskelly/status/1782535482720567687), a bunch of us at Shopify decided to try and improve their resilience with regards to ES module loading

Together with @jaffathecake we’ve put together a proposal doc https://docs.google.com/document/d/1J1SColgpcZoVjERs05HhhFivLmAySCCUT3rL4vT9XZg/edit?pli=1, ran it by the relevant folks, and got their thumbs-up on the general concept

@tomayac https://github.com/whatwg/html/pull/10528 is planned to change the "one import map per document" paradigm

@tomayac this was discussed during the pr review: https://github.com/whatwg/html/pull/10269#issuecomment-2048971280

Basically, it complicates the processing model, and doesn't provide significant benefits

I wrote a thing: Shipping ES module integrity in Chrome and Safari https://shopify.engineering/shipping-support-for-module-script-integrity-in-chrome-safari

@ksylor @FND @simevidas @nicj sounds interesting!! Happy to put this on the agenda for discussion at TPAC, if anyone's interested in presenting

@tomayac https://codereview.chromium.org/118011
The (predictable) answer is compat..