Re: [whatwg/url] Qualify exported URL terms that are too generic (#375)

Whatever you're doing as far as namespacing goes, it's hijacking `<a>fragment</a>` in all the CSS specs. Where it's used as a noun, I can disambiguate it as “box fragment” at the cost of a little wordiness, but there isn't much I can do where it's used as a verb, other than put in an explicit override to link it to css-break-3.  Which I'd be willing to live with if I didn't think that you shouldn't be exporting the term “fragment” when “URL fragment” would be a better term for cross-linking anyway. :)

> If you have a fragment, you likely want to qualify it with a `for` attribute too, to indicate what the fragment is part of.

`<dfn for="CSS">fragment</dfn>`? I mean, at that rate, I should have a `for` attribute on every exported term in the entire CSS specification corpus... Not that it'll help anything--afaict, the `for` attribute only works on syntactic constructs like methods, attributes, and property values, not regular terms. https://tabatkins.github.io/bikeshed/#autolinking

CC @tabatkins

-- 
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/url/issues/375#issuecomment-375855343