News for hackers. Stuff that matters.

A comment on Using the Topics API (Chrome Only, Opposed by Firefox/Safari). Parent comment

Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by bastawhiz on Monday September 16, 2024 @06:27AM (#41554616)
It's a proposal for a web technology. Every web technology starts as a proposal, even if nobody but a single vendor implements it. MDN includes documentation for serious proposals at all stages, regardless of the standardization process.

In fact, MDN includes non-standardized APIs as well. Browser-specific interfaces are included, because it turns out that if you only document the APIs that went through the standardization process and not the ones that actually exist, it makes for a bad documentation site.

[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by JimDabell on Tuesday September 17, 2024 @06:44AM (#41566279)
It’s a proposal that was rejected by everybody who isn’t Google. It isn’t going to be part of the web platform. It has exited the standardisation process. It’s at stage “never”. It belongs on MDN about as much as JSSS does.
[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by Dylan16807 on Tuesday September 17, 2024 @12:03PM (#41569120)
JSSS is long dead.

I'd say a better comparison is JSX, and searching for that I do see pages on MDN about it.

[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by bastawhiz on Tuesday September 17, 2024 @03:16PM (#41571559)
That doesn't change anything. Whether or not it ever ships doesn't mean it shouldn't be documented. There's zero cost to documenting it. Just because you don't like it and it didn't make it past the proposal stage doesn't mean it shouldn't be on MDN. That's not how MDN works.
[ Parent | on HN ]