You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bikeshed currently (on commit 6dfbdba) shows this error:
LINE ~3513: Multiple possible 'window' dfn refs.
Arbitrarily chose https://drafts.csswg.org/css-color-3/#window
To auto-select one of the following refs, insert one of these lines into a <pre class=link-defaults> block:
spec:css-color-3; type:dfn; text:window
spec:fetch; type:dfn; text:window
spec:screen-capture; type:dfn; text:window
[=Window=]
There is also a [=Document=] link in the same paragraph, which links to the documents concept in the DOM spec. I'm not sure if that ought to link to the Document interface too, but both are right next to each other either way.
Proposed Change
Change the [=Window=] links to {{Window}}, thus linking to the Window interface in the HTML spec.
There are references throughout the DOM spec such as "Each Window object has an associated current event", linking to the Window interface. So it seems like {{Window}} object is the preferred reference format, rather than linking to the window property.
The text was updated successfully, but these errors were encountered:
Bikeshed currently (on commit 6dfbdba) shows this error:
The spec text in question is:
And indeed, this quote from the current state of the editor's draft incorrectly links to "Window" in the CSS spec. L2 and L1 both link to "Window" in the Fetch spec, which also seems incorrect. It seems to me like this should probably point to either the
Window
interface or itswindow
property, both in the HTML spec.There is also a
[=Document=]
link in the same paragraph, which links to the documents concept in the DOM spec. I'm not sure if that ought to link to theDocument
interface too, but both are right next to each other either way.Proposed Change
Change the
[=Window=]
links to{{Window}}
, thus linking to theWindow
interface in the HTML spec.There are references throughout the DOM spec such as "Each Window object has an associated current event", linking to the
Window
interface. So it seems like{{Window}} object
is the preferred reference format, rather than linking to thewindow
property.The text was updated successfully, but these errors were encountered: