@openwebdocs is proposing the creation of a new Community Group at W3C: the Docs CG.

Its mission is to ensure that web developers and designers will have the best information available to them, so they can build for the web.

If you're interested in web documentation, either as a publisher or a consumer, please support the creation of this CG at https://www.w3.org/community/groups/proposed/

And, once it's created, please join the group! UPDATE: GROUP CREATED AT https://www.w3.org/community/docs-cg/

Servo Report Week 12 2025

Highlights from last week:

- Support align attribute on HTMLParagraphElement interface
- Implement declarative shadow DOM
- Implement the `fit-content()` sizing function
- Added --enable-experimental-web-platform-features command line argument

You can help support Servo, an independent web browser engine, and the health of the web ecosystem by donating:

GitHub: https://github.com/sponsors/servo
Open Collective: https://opencollective.com/servo

@servo DSD, nice!

For the first time in my life I have a horrible credit score,

just like that of the United States.

I'll definitely be turning on erasableSyntaxOnly:true in TypeScript 5.8! Very nice!

It enforces that all type definitions are annotations only, so when you strip the annotations, you end up with exactly the JavaScript you would have written without annotations (no enum, no namespace, etc)!

@shplink Weird indeed. I reported the bug and Google marked it as "Intended Behavior".

https://issuetracker.google.com/issues/389946229

More eason for me to keep their apps off my phones. I use only desktop web apps at the moment, with two Google Workspace subscriptions that I need to find replacements for.

All JavaScript runtimes/registries (Nodejs, Bun, Deno, NPM, JSR, etc) should @$%&ing support import maps as a source of truth for dependencies,

*without non-standard* additions, only URLs supported by every runtime including web browsers,

so we can be done with all the incompatibility bull@$%&.

<rant>

Doesn't matter how incredible someone's product is.

If I appear on their emailing list without my consent they get automatically reported as spam and trashed.

Stop that garbage!

</rant>

@shplink Nice. I've been doing this too. I have no more Google account on my Android phone. But even if I log into Google on a website in the phone browser, Google will restore push-based auth to my account despite that I'm not logged into the OS, effectively locking me out of all devices. Super annoying, and generally speaking I also want to regain my privacy. The biggest pain will be migrating Photos and Drive to something self hosted. Any recommendations?

@mrtrimble Those are good (bad) points. I would hate to be on a platform that tries to make me interact with fake (AI) people. That basically degrades it from useful to a game. AIs could potentially cause mass killings by unintentionally confirming or fabricating hate and making it spread.

And I got to work there for a bit, their web app infrastructure is an utter mess.

Literally a "profile pic" haha.

What compilers for `html` template strings exist besides Lit's?

I think this is a really good area to explore, and the IDE tooling for it so we can get type checking in the template strings for HTML elements. F.e.

Ok:

html`<some-el num=${5} />`

Type error:

html`<some-el num=${true} />`

@mrtrimble oh is it the blocking of pixelfed? If so, yeah, that a dumb move. People are starting to see right past that junk. They should compete instead of thinking blocking others is how to win.

@develwithoutacause Sounds like it would be nifty. How though? Would each browser have browser specific extension APIs? Would browser teams be willing to justify the support? Seems like improving custom elements APIs and devtools support for them (unique in each browser devtools) will at least be the way to do it in the most standard way with the least burden, just only supporting CE frameworks. Is there a clear way to do it for all frameworks in all browsers?

@mrtrimble what shenanigans out of curiosity?

@develwithoutacause chii can be seen in use on Solid.js playground:

https://playground.solidjs.com/

@develwithoutacause maybe Custom Elements are basically that common API. It might be non-ideal for browsers to support APIs for userland frameworks. But if the pieces for building element inspector are re-usable, then easier to make the tools. However devtools are not standardized across browsers *at all*. It would be a massive undertaking to standardize.

Open source devtools like chii might be useful (it's a standalone Chrome devtools fork that runs fully in browser):

https://github.com/liriliri/chii

@develwithoutacause kinda like matter and antimatter!

@JaneOri wow

@tchambers it has been broken for weeks: