Re: [whatwg/dom] Add caniuse info boxes like the HTML spec (#69)

> That does not help especially since Bikeshed is now mostly a server-side operation.

I don't understand what this means. Are you saying that you don't have a way to look at the warnings from Bikeshed?  Do I need to give you a flag that elevates warnings and link errors to be fatal, so they'll stop your auto-build?

> What we need is automatic cross-referencing.

And I've already explained why that doesn't actually work.

Even if I can fix some of the cross-ref issues (like the URLs that are to just a spec itself, not a particular anchor), there's no way to fix the problem that it's impossible to use on a spec published at more than one URL, which is the *common* case for W3C specs; if you move a spec, the panels just *stop working* until you write a Can I Use PR and get it accepted; if one of the features has its URL changed by someone else (not one of the spec editors), the panel just *silently disappears* until you notice and update Can I Use.

The current design is robust and easy to use.  It relies on the stable identifiers from the CanIUse db, so nothing will change underneath you unless Can I Use goes totally crazy; it lets you position the panel wherever you want; it lets you publish the same spec to multiple URLs and it continues working without any effort on your part; it now warns you if someone changes the URLs away or adds new features to the same URL, so you can tell when you need to fix something; and the markup you add to tag it in is small and simple.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/69#issuecomment-259780166

Received on Thursday, 10 November 2016 19:14:59 UTC