5 ms·
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 fo
by bastawhiz 2y ago
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.
- JimDabell 2y agoIt’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.
- Dylan16807 2y agoJSSS is long dead. I'd say a better comparison is JSX, and searching for that I do see pages on MDN about it.
- bastawhiz 2y agoThat 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.