- From: Tab Atkins Jr. <notifications@github.com>
- Date: Mon, 10 Oct 2016 14:11:40 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Message-ID: <whatwg/dom/issues/69/252747513@github.com>
That (Can I Use being updated) hasn't happened for most of the specs it covers; there's a bewildering variety of URLs there, including some that I never even realized were in use (`css3-webfonts`, for example). It's possible that using this feature will make people more cognizant, but I suspect the more common reaction will be to just copy/paste the URL from the old draft over - it still works, after all! As I said, the big thing I'm concerned about is Can I Use changing, and people not realizing that it did, thus losing the annotations. Most people don't seem to review diffs for the generated file, so it won't be noticed unless they happen to scroll by something that they know should have a CanIUse block and notice that it doesn't. I highly suspect this will happen when people "do the right thing" and update Can I Use with the new publication URL; any old drafts will stop showing annotations until the issue is noticed (if ever) and corrected. (This is especially problematic for CI-generated drafts.) There's additionally the placement problems that I alluded to previously - several of the CanIUse URLs do not have a fragment; they just have the bare spec URL. Some specs have both - one feature with just the bare URL, and then several with anchors pointing to the specific definition. It's unclear where that no-fragment annotation should be placed; if I choose a place by default, there will always be people who want something else. The "duplication" is super minor - you just add `caniuse="insert-adjacent"` to an element. Clear and small. I'm gonna go ahead and go with what I proposed in the compromise. It avoids all the problems of trying to auto-associate caniuse annotations to a spec via URL, while also avoiding the "I need to regularly poll CanIUse to see if any new features of my specs are supported", as long as the URLs are set up properly (which is a requirement of either proposal). -- 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-252747513
Received on Monday, 10 October 2016 21:12:35 UTC