Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

html5.1 branch & bikeshed FATAL ERROR #707

Closed
fititnt opened this issue Nov 6, 2016 · 7 comments
Closed

html5.1 branch & bikeshed FATAL ERROR #707

fititnt opened this issue Nov 6, 2016 · 7 comments
Assignees
@travisleithead
Labels
bikeshed

Comments

@fititnt
Copy link

fititnt commented Nov 6, 2016

html5.1 branch (HTML 5.1 W3C Recommendation) apparently have some bikeshed errors, and ideally should be tested by a different to reconfirm if is not just my mistake. I used the same deploy scripts with a few changes,

Logs

Using worker: worker-linux-docker-80b78178.prod.travis-ci.org:travis-linux-8
(...)
$ git clone --depth=50 --branch=html5.1-translation-pt https://github.com/fititnt/html51-translation-testing.git fititnt/html51-translation-testing
(...)
$ git clone --depth=100 --branch=master https://github.com/tabatkins/bikeshed.git ./bikeshed
(...)
$ pip install --editable ./bikeshed
$ bikeshed update
$ bikeshed -f spec && ./.multipage-split.sh
WARNING: You should manually provide IDs for your headings:
  <h3 class="heading" id="features-added"><span class="content">Features added</span></h3>
  <h3 class="heading" id="features-removed"><span class="content">Features removed</span></h3>
  <h3 class="heading" id="changes-to-existing-features"><span class="content">Changes to existing features</span></h3>
FATAL ERROR: 'element' definitions don't use a 'for' attribute, but this one claims it's for 'conventions' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-noexport="" data-dfn-type="element"><code>this</code></dfn>
FATAL ERROR: 'element' definitions don't use a 'for' attribute, but this one claims it's for 'global' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="element" data-dfn-for="global"><code>xml:base</code></dfn>
FATAL ERROR: 'element' definitions don't use a 'for' attribute, but this one claims it's for 'picture' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="picture source" data-dfn-type="element" data-dfn-for="picture"><code>source</code></dfn>
FATAL ERROR: 'element' definitions don't use a 'for' attribute, but this one claims it's for 'media' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="element" data-dfn-for="media"><code>source</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrackMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="TextTrackMode"><code>disabled</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrackMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="TextTrackMode"><code>hidden</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrackMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="TextTrackMode"><code>showing</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'SelectionMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="SelectionMode"><code>select</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'SelectionMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="SelectionMode"><code>start</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'SelectionMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="SelectionMode"><code>end</code></dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'SelectionMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-dfn-type="enum" data-dfn-for="SelectionMode"><code>preserve</code></dfn>
WARNING: Multiple elements have the same ID 'link'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'required'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'focus'.
Deduping, but this ID may not be stable across revisions.
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLAllCollection' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLAllCollection" class="nv" data-dfn-type="interface">HTMLAllCollection</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLFormControlsCollection' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLFormControlsCollection" class="nv" data-dfn-type="interface">HTMLFormControlsCollection</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'RadioNodeList' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="RadioNodeList" class="nv" data-dfn-type="interface">RadioNodeList</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLOptionsCollection' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLOptionsCollection" class="nv" data-dfn-type="interface">HTMLOptionsCollection</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DOMStringMap' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DOMStringMap" class="nv" data-dfn-type="interface">DOMStringMap</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DOMElementMap' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DOMElementMap" class="nv" data-dfn-type="interface">DOMElementMap</dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'Document' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DocumentReadyState" class="nv" data-dfn-type="enum">DocumentReadyState</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLElement" class="nv" data-dfn-type="interface">HTMLElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLUnknownElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLUnknownElement" class="nv" data-dfn-type="interface">HTMLUnknownElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLHtmlElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLHtmlElement" class="nv" data-dfn-type="interface">HTMLHtmlElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLHeadElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLHeadElement" class="nv" data-dfn-type="interface">HTMLHeadElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTitleElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTitleElement" class="nv" data-dfn-type="interface">HTMLTitleElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLBaseElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLBaseElement" class="nv" data-dfn-type="interface">HTMLBaseElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLLinkElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLLinkElement" class="nv" data-dfn-type="interface">HTMLLinkElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMetaElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMetaElement" class="nv" data-dfn-type="interface">HTMLMetaElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLStyleElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLStyleElement" class="nv" data-dfn-type="interface">HTMLStyleElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLBodyElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLBodyElement" class="nv" data-dfn-type="interface">HTMLBodyElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLHeadingElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLHeadingElement" class="nv" data-dfn-type="interface">HTMLHeadingElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLParagraphElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLParagraphElement" class="nv" data-dfn-type="interface">HTMLParagraphElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLHRElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLHRElement" class="nv" data-dfn-type="interface">HTMLHRElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLPreElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLPreElement" class="nv" data-dfn-type="interface">HTMLPreElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLQuoteElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLQuoteElement" class="nv" data-dfn-type="interface">HTMLQuoteElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLOListElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLOListElement" class="nv" data-dfn-type="interface">HTMLOListElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLUListElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLUListElement" class="nv" data-dfn-type="interface">HTMLUListElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLLIElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLLIElement" class="nv" data-dfn-type="interface">HTMLLIElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLDListElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLDListElement" class="nv" data-dfn-type="interface">HTMLDListElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLDivElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLDivElement" class="nv" data-dfn-type="interface">HTMLDivElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLAnchorElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLAnchorElement" class="nv" data-dfn-type="interface">HTMLAnchorElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLDataElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLDataElement" class="nv" data-dfn-type="interface">HTMLDataElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTimeElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTimeElement" class="nv" data-dfn-type="interface">HTMLTimeElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLSpanElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLSpanElement" class="nv" data-dfn-type="interface">HTMLSpanElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLBRElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLBRElement" class="nv" data-dfn-type="interface">HTMLBRElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLModElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLModElement" class="nv" data-dfn-type="interface">HTMLModElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLPictureElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLPictureElement" class="nv" data-dfn-type="interface">HTMLPictureElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLImageElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLImageElement" class="nv" data-dfn-type="interface">HTMLImageElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLIFrameElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLIFrameElement" class="nv" data-dfn-type="interface">HTMLIFrameElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLEmbedElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLEmbedElement" class="nv" data-dfn-type="interface">HTMLEmbedElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLObjectElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLObjectElement" class="nv" data-dfn-type="interface">HTMLObjectElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLParamElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLParamElement" class="nv" data-dfn-type="interface">HTMLParamElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLVideoElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLVideoElement" class="nv" data-dfn-type="interface">HTMLVideoElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLAudioElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLAudioElement" class="nv" data-dfn-type="interface">HTMLAudioElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLSourceElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLSourceElement" class="nv" data-dfn-type="interface">HTMLSourceElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTrackElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTrackElement" class="nv" data-dfn-type="interface">HTMLTrackElement</dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'CanPlayTypeResult' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="CanPlayTypeResult" class="nv" data-dfn-type="enum">CanPlayTypeResult</dfn>
FATAL ERROR: 'typedef' definitions don't use a 'for' attribute, but this one claims it's for 'MediaProvider' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="MediaProvider" class="nv" data-dfn-type="typedef">MediaProvider</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMediaElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMediaElement" class="nv" data-dfn-type="interface">HTMLMediaElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'MediaError' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="MediaError" class="nv" data-dfn-type="interface">MediaError</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'AudioTrackList' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="AudioTrackList" class="nv" data-dfn-type="interface">AudioTrackList</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'AudioTrack' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="AudioTrack" class="nv" data-dfn-type="interface">AudioTrack</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'VideoTrackList' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="VideoTrackList" class="nv" data-dfn-type="interface">VideoTrackList</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'VideoTrack' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="VideoTrack" class="nv" data-dfn-type="interface">VideoTrack</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrackList' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TextTrackList" class="nv" data-dfn-type="interface">TextTrackList</dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrack' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TextTrackMode" class="nv" data-dfn-type="enum">TextTrackMode</dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrack' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TextTrackKind" class="nv" data-dfn-type="enum">TextTrackKind</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrack' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TextTrack" class="nv" data-dfn-type="interface">TextTrack</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrackCueList' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TextTrackCueList" class="nv" data-dfn-type="interface">TextTrackCueList</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'TextTrackCue' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TextTrackCue" class="nv" data-dfn-type="interface">TextTrackCue</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DataCue' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DataCue" class="nv" data-dfn-type="interface">DataCue</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'TimeRanges' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TimeRanges" class="nv" data-dfn-type="interface">TimeRanges</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'TrackEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TrackEvent" class="nv" data-dfn-type="interface">TrackEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'TrackEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="TrackEventInit" class="nv" data-dfn-type="dictionary">TrackEventInit</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMapElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMapElement" class="nv" data-dfn-type="interface">HTMLMapElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLAreaElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLAreaElement" class="nv" data-dfn-type="interface">HTMLAreaElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLHyperlinkElementUtils' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLHyperlinkElementUtils" class="nv" data-dfn-type="interface">HTMLHyperlinkElementUtils</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableElement" class="nv" data-dfn-type="interface">HTMLTableElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableCaptionElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableCaptionElement" class="nv" data-dfn-type="interface">HTMLTableCaptionElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableColElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableColElement" class="nv" data-dfn-type="interface">HTMLTableColElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableSectionElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableSectionElement" class="nv" data-dfn-type="interface">HTMLTableSectionElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableRowElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableRowElement" class="nv" data-dfn-type="interface">HTMLTableRowElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableDataCellElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableDataCellElement" class="nv" data-dfn-type="interface">HTMLTableDataCellElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableHeaderCellElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableHeaderCellElement" class="nv" data-dfn-type="interface">HTMLTableHeaderCellElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTableCellElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTableCellElement" class="nv" data-dfn-type="interface">HTMLTableCellElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLFormElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLFormElement" class="nv" data-dfn-type="interface">HTMLFormElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLLabelElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLLabelElement" class="nv" data-dfn-type="interface">HTMLLabelElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLInputElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLInputElement" class="nv" data-dfn-type="interface">HTMLInputElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLButtonElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLButtonElement" class="nv" data-dfn-type="interface">HTMLButtonElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLSelectElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLSelectElement" class="nv" data-dfn-type="interface">HTMLSelectElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLDataListElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLDataListElement" class="nv" data-dfn-type="interface">HTMLDataListElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLOptGroupElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLOptGroupElement" class="nv" data-dfn-type="interface">HTMLOptGroupElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLOptionElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLOptionElement" class="nv" data-dfn-type="interface">HTMLOptionElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTextAreaElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTextAreaElement" class="nv" data-dfn-type="interface">HTMLTextAreaElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLKeygenElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLKeygenElement" class="nv" data-dfn-type="interface">HTMLKeygenElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLOutputElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLOutputElement" class="nv" data-dfn-type="interface">HTMLOutputElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLProgressElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLProgressElement" class="nv" data-dfn-type="interface">HTMLProgressElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMeterElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMeterElement" class="nv" data-dfn-type="interface">HTMLMeterElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLFieldSetElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLFieldSetElement" class="nv" data-dfn-type="interface">HTMLFieldSetElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLLegendElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLLegendElement" class="nv" data-dfn-type="interface">HTMLLegendElement</dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'SelectionMode' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="SelectionMode" class="nv" data-dfn-type="enum">SelectionMode</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'ValidityState' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ValidityState" class="nv" data-dfn-type="interface">ValidityState</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLDetailsElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLDetailsElement" class="nv" data-dfn-type="interface">HTMLDetailsElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMenuElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMenuElement" class="nv" data-dfn-type="interface">HTMLMenuElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMenuItemElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMenuItemElement" class="nv" data-dfn-type="interface">HTMLMenuItemElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'RelatedEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="RelatedEvent" class="nv" data-dfn-type="interface">RelatedEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'RelatedEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="RelatedEventInit" class="nv" data-dfn-type="dictionary">RelatedEventInit</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLScriptElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLScriptElement" class="nv" data-dfn-type="interface">HTMLScriptElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLTemplateElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLTemplateElement" class="nv" data-dfn-type="interface">HTMLTemplateElement</dfn>
FATAL ERROR: 'typedef' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLCanvasElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="RenderingContext" class="nv" data-dfn-type="typedef">RenderingContext</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLCanvasElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLCanvasElement" class="nv" data-dfn-type="interface">HTMLCanvasElement</dfn>
FATAL ERROR: 'callback' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLCanvasElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="BlobCallback" class="nv" data-dfn-type="callback">BlobCallback</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'ElementContentEditable' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ElementContentEditable" class="nv" data-dfn-type="interface">ElementContentEditable</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DataTransfer' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DataTransfer" class="nv" data-dfn-type="interface">DataTransfer</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DataTransferItemList' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DataTransferItemList" class="nv" data-dfn-type="interface">DataTransferItemList</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DataTransferItem' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DataTransferItem" class="nv" data-dfn-type="interface">DataTransferItem</dfn>
FATAL ERROR: 'callback' definitions don't use a 'for' attribute, but this one claims it's for 'DataTransferItem' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="FunctionStringCallback" class="nv" data-dfn-type="callback">FunctionStringCallback</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DragEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DragEvent" class="nv" data-dfn-type="interface">DragEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'DragEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DragEventInit" class="nv" data-dfn-type="dictionary">DragEventInit</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'Window' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="Window" class="nv" data-dfn-type="interface">Window</dfn>
FATAL ERROR: 'callback' definitions don't use a 'for' attribute, but this one claims it's for 'Window' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="FrameRequestCallback" class="nv" data-dfn-type="callback">FrameRequestCallback</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'BarProp' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="BarProp" class="nv" data-dfn-type="interface">BarProp</dfn>
FATAL ERROR: 'enum' definitions don't use a 'for' attribute, but this one claims it's for 'ScrollRestoration' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ScrollRestoration" class="nv" data-dfn-type="enum">ScrollRestoration</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'History' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="History" class="nv" data-dfn-type="interface">History</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'Location' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="Location" class="nv" data-dfn-type="interface">Location</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'PopStateEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="PopStateEvent" class="nv" data-dfn-type="interface">PopStateEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'PopStateEventInit' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="PopStateEventInit" class="nv" data-dfn-type="dictionary">PopStateEventInit</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HashChangeEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HashChangeEvent" class="nv" data-dfn-type="interface">HashChangeEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'HashChangeEventInit' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HashChangeEventInit" class="nv" data-dfn-type="dictionary">HashChangeEventInit</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'PageTransitionEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="PageTransitionEvent" class="nv" data-dfn-type="interface">PageTransitionEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'PageTransitionEventInit' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="PageTransitionEventInit" class="nv" data-dfn-type="dictionary">PageTransitionEventInit</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'BeforeUnloadEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="BeforeUnloadEvent" class="nv" data-dfn-type="interface">BeforeUnloadEvent</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'NavigatorOnLine' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="NavigatorOnLine" class="nv" data-dfn-type="interface">NavigatorOnLine</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'ErrorEvent' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ErrorEvent" class="nv" data-dfn-type="interface">ErrorEvent</dfn>
FATAL ERROR: 'dictionary' definitions don't use a 'for' attribute, but this one claims it's for 'ErrorEventInit' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ErrorEventInit" class="nv" data-dfn-type="dictionary">ErrorEventInit</dfn>
FATAL ERROR: 'callback' definitions don't use a 'for' attribute, but this one claims it's for 'EventHandlerNonNull' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="EventHandlerNonNull" class="nv" data-dfn-type="callback">EventHandlerNonNull</dfn>
FATAL ERROR: 'typedef' definitions don't use a 'for' attribute, but this one claims it's for 'EventHandlerNonNull' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="EventHandler" class="nv" data-dfn-type="typedef">EventHandler</dfn>
FATAL ERROR: 'callback' definitions don't use a 'for' attribute, but this one claims it's for 'OnErrorEventHandlerNonNull' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="OnErrorEventHandlerNonNull" class="nv" data-dfn-type="callback">OnErrorEventHandlerNonNull</dfn>
FATAL ERROR: 'typedef' definitions don't use a 'for' attribute, but this one claims it's for 'OnErrorEventHandlerNonNull' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="OnErrorEventHandler" class="nv" data-dfn-type="typedef">OnErrorEventHandler</dfn>
FATAL ERROR: 'callback' definitions don't use a 'for' attribute, but this one claims it's for 'OnBeforeUnloadEventHandlerNonNull' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="OnBeforeUnloadEventHandlerNonNull" class="nv" data-dfn-type="callback">OnBeforeUnloadEventHandlerNonNull</dfn>
FATAL ERROR: 'typedef' definitions don't use a 'for' attribute, but this one claims it's for 'OnBeforeUnloadEventHandlerNonNull' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="OnBeforeUnloadEventHandler" class="nv" data-dfn-type="typedef">OnBeforeUnloadEventHandler</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'GlobalEventHandlers' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="GlobalEventHandlers" class="nv" data-dfn-type="interface">GlobalEventHandlers</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'WindowEventHandlers' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="WindowEventHandlers" class="nv" data-dfn-type="interface">WindowEventHandlers</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'DocumentAndElementEventHandlers' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="DocumentAndElementEventHandlers" class="nv" data-dfn-type="interface">DocumentAndElementEventHandlers</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'WindowBase64' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="WindowBase64" class="nv" data-dfn-type="interface">WindowBase64</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'WindowTimers' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="WindowTimers" class="nv" data-dfn-type="interface">WindowTimers</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'WindowModal' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="WindowModal" class="nv" data-dfn-type="interface">WindowModal</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'Navigator' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="Navigator" class="nv" data-dfn-type="interface">Navigator</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'NavigatorID' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="NavigatorID" class="nv" data-dfn-type="interface">NavigatorID</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'NavigatorLanguage' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="NavigatorLanguage" class="nv" data-dfn-type="interface">NavigatorLanguage</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'NavigatorContentUtils' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="NavigatorContentUtils" class="nv" data-dfn-type="interface">NavigatorContentUtils</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'NavigatorCookies' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="NavigatorCookies" class="nv" data-dfn-type="interface">NavigatorCookies</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'NavigatorPlugins' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="NavigatorPlugins" class="nv" data-dfn-type="interface">NavigatorPlugins</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'PluginArray' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="PluginArray" class="nv" data-dfn-type="interface">PluginArray</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'MimeTypeArray' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="MimeTypeArray" class="nv" data-dfn-type="interface">MimeTypeArray</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'Plugin' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="Plugin" class="nv" data-dfn-type="interface">Plugin</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'MimeType' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="MimeType" class="nv" data-dfn-type="interface">MimeType</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'ImageBitmap' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ImageBitmap" class="nv" data-dfn-type="interface">ImageBitmap</dfn>
FATAL ERROR: 'typedef' definitions don't use a 'for' attribute, but this one claims it's for 'ImageBitmap' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ImageBitmapSource" class="nv" data-dfn-type="typedef">ImageBitmapSource</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'ImageBitmapFactories' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ImageBitmapFactories" class="nv" data-dfn-type="interface">ImageBitmapFactories</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLAppletElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLAppletElement" class="nv" data-dfn-type="interface">HTMLAppletElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLMarqueeElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLMarqueeElement" class="nv" data-dfn-type="interface">HTMLMarqueeElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLFrameSetElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLFrameSetElement" class="nv" data-dfn-type="interface">HTMLFrameSetElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLFrameElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLFrameElement" class="nv" data-dfn-type="interface">HTMLFrameElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'ApplicationCache' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="ApplicationCache" class="nv" data-dfn-type="interface">ApplicationCache</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLDirectoryElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLDirectoryElement" class="nv" data-dfn-type="interface">HTMLDirectoryElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'HTMLFontElement' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="HTMLFontElement" class="nv" data-dfn-type="interface">HTMLFontElement</dfn>
FATAL ERROR: 'interface' definitions don't use a 'for' attribute, but this one claims it's for 'Extenal' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-lt="External" class="nv" data-dfn-type="interface">External</dfn>
[1;33mLINK ERROR: No 'dfn' refs found for 'name' with spec 'dom-ls'.
[1;33mLINK ERROR: No 'dfn' refs found for 'absolute url' that are marked for export.
[1;33mLINK ERROR: No 'dfn' refs found for 'relative url' that are marked for export.
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="dfn" data-lt="URL serializer">URL serializer</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="dfn" data-lt="append">append</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="dfn" data-lt="replace">replace</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-lt="write()" data-link-type="method"><code>document.write()</code></a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="dfn" data-lt="removed">removed</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="dfn" data-lt="inserted">inserted</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="dfn" data-lt="Adopt">Adopt</a>
[1;33mLINK ERROR: No 'dfn' refs found for 'absolute urls' that are marked for export.
[1;33mLINK ERROR: No 'dfn' refs found for 'relative urls' that are marked for export.
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-link-type="element" data-lt="desc">desc</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-lt="write()" data-link-type="method">new characters
    to be inserted into the tokenizer</a>
[1;33mLINK ERROR: Ambiguous for-less link, please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
<a data-lt="write()" data-link-type="method">new characters to be
    inserted into the tokenizer</a>
[1;33mLINK ERROR: No 'idl' refs found for 'requestAnimationFrame'.
[1;33mLINK ERROR: No 'idl' refs found for 'enqueueJob'.
[1;33mLINK ERROR: No 'idl' refs found for 'nextJob'.
[1;33mLINK ERROR: Multiple possible 'idl' local refs for 'currentSrc'.
Arbitrarily chose the one with type 'attribute' and for 'HTMLImageElement'.
[1;33mLINK ERROR: Multiple possible 'idl' refs for 'script'.
Arbitrarily chose the one in fetch.
If this is wrong, insert one of the following lines into a <pre class=link-defaults> block:
spec:fetch; type:enum-value; for:RequestDestination; text:script
spec:fetch; type:enum-value; for:RequestType; text:script
[7;32m ✔  Successfully generated, but fatal errors were suppressed
rm -rf out
mkdir out
@fititnt fititnt mentioned this issue Nov 6, 2016
Merged
@travisleithead
Copy link
Member

I just tried to build the 5.1 branch (using the latest live bikeshed bits), and got the following:

WARNING: [0m You should manually provide IDs for your headings:
  <h3 class="heading" id="features-removed"><span class="content">Features removed</span></h3>
  <h3 class="heading" id="features-added"><span class="content">Features added</span></h3>
  <h3 class="heading" id="changes-to-existing-features"><span class="content">Changes to existing features</span></h3>
 [1;31mFATAL ERROR: [0m 'element' definitions don't use a 'for' attribute, but this one claims it's for 'conventions' (perhaps inherited from an ancestor). This is probably a markup error.
<dfn data-noexport="" data-dfn-type="element"><code>this</code></dfn>

I'm seeing if there's a simple fix for this now...

@travisleithead
Copy link
Member

This appears to be due to elements with a dfn-for= attribute which inherits down to dfns within its scope specifically for element definitions. When I remove the inheriting attribute (transferring it to individual dfns (manually inheriting it to dfns other than element the error goes away. See https://github.com/travisleithead/html/commit/b59f37a5056dfa1875328d428bcc1ca49d198f53

@travisleithead
Copy link
Member

@arronei would you take a look? Did bikeshed regress this functionality?

@travisleithead
Copy link
Member

OK. This passes in the build system because we're checking out a specific (past) version of Bikeshed prior to some changes that both improved and tightened some of the authoring requirements on the use of Bikeshed.

I'm not going to try to update the 5.1 branch to be conforming, because we've pushed it to rec, and the changes I'm making in master to pass with the latest Bikeshed are in at least one case pretty dramatic. So, instead, I'll update the Readme page (in that branch) to be very specific about which Bikeshed version to use:

  1. Install Bikeshed (using the usual methods)

  2. Checkout the past version of bikeshed used to generate HTML5.1:

    git checkout 0dca46a2874cdca2aa5e27d33d9a000f1e1b6e45

  3. Copy and replace bikeshed's own copy of its spec-data folder with the contents cached in the HTML repo, HTML5.1 branch). From the html repo directory:

    cp -R .spec-data/* [path to bikeshed repo]/bikeshed/spec-data

For the master branch, I'm preparing a change to update the spec to fix the rest of the Fatal errors.

This was referenced Nov 15, 2016
Closed
Merged
Merged
@fititnt fititnt mentioned this issue Nov 15, 2016
Merged
@chaals
Copy link
Collaborator

chaals commented Nov 17, 2016

Can we close the issue?

@fititnt
Copy link
Author

fititnt commented Nov 17, 2016

I guess we should close it. This need documentation, but this is another issue (# 676) but this problem was just about the fatal errors.

@fititnt fititnt closed this as completed Nov 17, 2016
@chaals
Copy link
Collaborator

chaals commented Nov 17, 2016

OK, thanks.

And thanks @travisleithead for fixing it :)

stevefaulkner pushed a commit that referenced this issue Nov 29, 2016
@travisleithead @stevefaulkner
Fix all FATAL ERRORs when using the latest [evergreen] bikeshed in ma…
524b1ef 
…ster branch (#727)

* Fix #707

Fix #707

Bikeshed updates have made the following unnecessary:
1. idl dfn attributes to mark which interface they use
2. for attributes on elements -- reworking the two cases we have in the
spec for this (source and title)
Found other bugs exposed by this bikeshed update in our spec, namely
around use of enum, that should have been enum-value.

* Finish merge of <source> element, and related cleanup.

* final changes to fix fatal-errors during build process
arronei pushed a commit to arronei/html that referenced this issue Apr 17, 2017
@travisleithead @arronei
Fix all FATAL ERRORs when using the latest [evergreen] bikeshed in ma…
5a8f869 
…ster branch (w3c#727)

* Fix w3c#707

Fix w3c#707

Bikeshed updates have made the following unnecessary:
1. idl dfn attributes to mark which interface they use
2. for attributes on elements -- reworking the two cases we have in the
spec for this (source and title)
Found other bugs exposed by this bikeshed update in our spec, namely
around use of enum, that should have been enum-value.

* Finish merge of <source> element, and related cleanup.

* final changes to fix fatal-errors during build process
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@travisleithead travisleithead

Labels
bikeshed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@fititnt @travisleithead @arronei @chaals