Skip to content
Permalink
Browse files

[e] (0) Remove some last traces of XBL.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24261
Affected topics: Canvas, DOM APIs, HTML, Rendering

git-svn-id: http://svn.whatwg.org/webapps@8395 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 14, 2014
1 parent e49cdf0 commit d92962f32bd79a06c75b4186fbdbef827e7a84ab
Showing with 36 additions and 36 deletions.
  1. +12 −12 complete.html
  2. +12 −12 index
  3. +12 −12 source
relative to other specifications can be best summed up as
follows:</p>

<p><img src=http://images.whatwg.org/abstract.png width=398 alt="It consists of everything else, above such core technologies as HTTP, URI/IRIs, DOM, XML, Unicode, and ECMAScript; below presentation-layer technologies like CSS, XBL, and the NPAPI; and to the side of technologies like Geolocation, SVG, MathML, and XHR." height=359></p>
<p><img src=http://images.whatwg.org/abstract.png width=398 alt="It consists of everything else, above such core technologies as HTTP, URI/IRIs, DOM, XML, Unicode, and ECMAScript; below presentation-layer technologies like CSS and the NPAPI; and to the side of technologies like Geolocation, SVG, MathML, and XHR." height=359></p>



element is available. For example, it is inappropriate to use a <code><a href=#the-canvas-element>canvas</a></code> element to
render a page heading: if the desired presentation of the heading is graphically intense, it
should be marked up using appropriate elements (typically <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>) and then styled using
CSS and supporting technologies such as XBL.</p>
CSS and supporting technologies such as Web Components.</p>

<p>When authors use the <code><a href=#the-canvas-element>canvas</a></code> element, they must also provide content that, when
presented to the user, conveys essentially the same function or purpose as the
a document">inserted into the document</a>, the user agent must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache selection algorithm</a> with no manifest, and
passing in the <code><a href=#document>Document</a></code>.</p>

<!--CLEANUP-->
<p class=note>Because the processing of the <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code>
attribute happens only once the root element is parsed, any URLs referenced by processing
instructions before the root element (such as <code title="">&lt;?xml-stylesheet?&gt;</code> and
<code title="">&lt;?xbl?&gt;</code> PIs) will be fetched from the network and cannot be
instructions before the root element (such as <code title="">&lt;?xml-stylesheet?&gt;</code> PIs) will be fetched from the network and cannot be
cached.</p><!-- v2: fix this somehow -->

<p>User agents may examine the namespace of the root <code><a href=#element>Element</a></code> node of this
parsing, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>

<p>User agents may add content to the <code><a href=#the-head-element>head</a></code> element of the <code><a href=#document>Document</a></code>, e.g.
linking to a style sheet or an XBL binding, providing script, giving the document a
linking to a style sheet or a binding, providing script, giving the document a
<code><a href=#the-title-element>title</a></code>, etc.</p>

<p class=note>In particular, if the user agent supports the <code title="">Format=Flowed</code>
feature of RFC 3676 then the user agent would need to apply extra styling to cause the text to
wrap correctly and to handle the quoting feature. This could be performed using, e.g., an XBL
wrap correctly and to handle the quoting feature. This could be performed using, e.g., a
binding or a CSS extension.</p>

<p>The <a href=#task-source>task source</a> for the two tasks mentioned in this section must be the
fully loading, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>

<p>User agents may add content to the <code><a href=#the-head-element>head</a></code> element of the <code><a href=#document>Document</a></code>, or
attributes to the element <var title="">host element</var>, e.g. to link to a style sheet or an
XBL binding, to provide a script, to give the document a <code><a href=#the-title-element>title</a></code>, to make the media
attributes to the element <var title="">host element</var>, e.g. to link to a style sheet or a
binding, to provide a script, to give the document a <code><a href=#the-title-element>title</a></code>, to make the media
<a href=#attr-media-autoplay title=attr-media-autoplay>autoplay</a>, etc.</p>


fully loading, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>

<p>User agents may add content to the <code><a href=#the-head-element>head</a></code> element of the <code><a href=#document>Document</a></code>, or
attributes to the <code><a href=#the-embed-element>embed</a></code> element, e.g. to link to a style sheet or an XBL binding, or
attributes to the <code><a href=#the-embed-element>embed</a></code> element, e.g. to link to a style sheet or a binding, or
to give the document a <code><a href=#the-title-element>title</a></code>.</p>

<p class=note id=sandboxPluginNavigate>If the <code><a href=#document>Document</a></code>'s <a href=#active-sandboxing-flag-set>active sandboxing
<li>Event handlers, whether registered through the DOM using <code title="">addEventListener()</code>, by explicit <a href=#event-handler-content-attributes>event handler content attributes</a>, by
<a href=#event-handler-idl-attributes>event handler IDL attributes</a>, or otherwise.</li>

<li>Processing of technologies like XBL or SVG that have their own scripting features.</li>
<li>Processing of technologies like SVG that have their own scripting features.</li>

</ul><div class=impl>

input:not([type=image]), textarea { box-sizing: border-box; }</pre>

<p>Each kind of form control is also given a specific default binding, as described in subsequent
sections, which implements the look and feel of the control.</p>
sections, which implements the look and feel of the control.</p> <!-- a binding -->




<div class=impl>

<h3 id=bindings><span class=secno>14.5 </span>Bindings</h3>
<h3 id=bindings><span class=secno>14.5 </span>Bindings</h3> <!-- a binding -->

<h4 id=introduction-14><span class=secno>14.5.1 </span>Introduction</h4>

24 index
relative to other specifications can be best summed up as
follows:</p>

<p><img src=http://images.whatwg.org/abstract.png width=398 alt="It consists of everything else, above such core technologies as HTTP, URI/IRIs, DOM, XML, Unicode, and ECMAScript; below presentation-layer technologies like CSS, XBL, and the NPAPI; and to the side of technologies like Geolocation, SVG, MathML, and XHR." height=359></p>
<p><img src=http://images.whatwg.org/abstract.png width=398 alt="It consists of everything else, above such core technologies as HTTP, URI/IRIs, DOM, XML, Unicode, and ECMAScript; below presentation-layer technologies like CSS and the NPAPI; and to the side of technologies like Geolocation, SVG, MathML, and XHR." height=359></p>



element is available. For example, it is inappropriate to use a <code><a href=#the-canvas-element>canvas</a></code> element to
render a page heading: if the desired presentation of the heading is graphically intense, it
should be marked up using appropriate elements (typically <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code>) and then styled using
CSS and supporting technologies such as XBL.</p>
CSS and supporting technologies such as Web Components.</p>

<p>When authors use the <code><a href=#the-canvas-element>canvas</a></code> element, they must also provide content that, when
presented to the user, conveys essentially the same function or purpose as the
a document">inserted into the document</a>, the user agent must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache selection algorithm</a> with no manifest, and
passing in the <code><a href=#document>Document</a></code>.</p>

<!--CLEANUP-->
<p class=note>Because the processing of the <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code>
attribute happens only once the root element is parsed, any URLs referenced by processing
instructions before the root element (such as <code title="">&lt;?xml-stylesheet?&gt;</code> and
<code title="">&lt;?xbl?&gt;</code> PIs) will be fetched from the network and cannot be
instructions before the root element (such as <code title="">&lt;?xml-stylesheet?&gt;</code> PIs) will be fetched from the network and cannot be
cached.</p><!-- v2: fix this somehow -->

<p>User agents may examine the namespace of the root <code><a href=#element>Element</a></code> node of this
parsing, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>

<p>User agents may add content to the <code><a href=#the-head-element>head</a></code> element of the <code><a href=#document>Document</a></code>, e.g.
linking to a style sheet or an XBL binding, providing script, giving the document a
linking to a style sheet or a binding, providing script, giving the document a
<code><a href=#the-title-element>title</a></code>, etc.</p>

<p class=note>In particular, if the user agent supports the <code title="">Format=Flowed</code>
feature of RFC 3676 then the user agent would need to apply extra styling to cause the text to
wrap correctly and to handle the quoting feature. This could be performed using, e.g., an XBL
wrap correctly and to handle the quoting feature. This could be performed using, e.g., a
binding or a CSS extension.</p>

<p>The <a href=#task-source>task source</a> for the two tasks mentioned in this section must be the
fully loading, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>

<p>User agents may add content to the <code><a href=#the-head-element>head</a></code> element of the <code><a href=#document>Document</a></code>, or
attributes to the element <var title="">host element</var>, e.g. to link to a style sheet or an
XBL binding, to provide a script, to give the document a <code><a href=#the-title-element>title</a></code>, to make the media
attributes to the element <var title="">host element</var>, e.g. to link to a style sheet or a
binding, to provide a script, to give the document a <code><a href=#the-title-element>title</a></code>, to make the media
<a href=#attr-media-autoplay title=attr-media-autoplay>autoplay</a>, etc.</p>


fully loading, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>

<p>User agents may add content to the <code><a href=#the-head-element>head</a></code> element of the <code><a href=#document>Document</a></code>, or
attributes to the <code><a href=#the-embed-element>embed</a></code> element, e.g. to link to a style sheet or an XBL binding, or
attributes to the <code><a href=#the-embed-element>embed</a></code> element, e.g. to link to a style sheet or a binding, or
to give the document a <code><a href=#the-title-element>title</a></code>.</p>

<p class=note id=sandboxPluginNavigate>If the <code><a href=#document>Document</a></code>'s <a href=#active-sandboxing-flag-set>active sandboxing
<li>Event handlers, whether registered through the DOM using <code title="">addEventListener()</code>, by explicit <a href=#event-handler-content-attributes>event handler content attributes</a>, by
<a href=#event-handler-idl-attributes>event handler IDL attributes</a>, or otherwise.</li>

<li>Processing of technologies like XBL or SVG that have their own scripting features.</li>
<li>Processing of technologies like SVG that have their own scripting features.</li>

</ul><div class=impl>

input:not([type=image]), textarea { box-sizing: border-box; }</pre>

<p>Each kind of form control is also given a specific default binding, as described in subsequent
sections, which implements the look and feel of the control.</p>
sections, which implements the look and feel of the control.</p> <!-- a binding -->




<div class=impl>

<h3 id=bindings><span class=secno>14.5 </span>Bindings</h3>
<h3 id=bindings><span class=secno>14.5 </span>Bindings</h3> <!-- a binding -->

<h4 id=introduction-14><span class=secno>14.5.1 </span>Introduction</h4>

24 source
relative to other specifications can be best summed up as
follows:</p>

<p><img src="images/abstract.png" width="398" height="359" alt="It consists of everything else, above such core technologies as HTTP, URI/IRIs, DOM, XML, Unicode, and ECMAScript; below presentation-layer technologies like CSS, XBL, and the NPAPI; and to the side of technologies like Geolocation, SVG, MathML, and XHR."></p>
<p><img src="images/abstract.png" width="398" height="359" alt="It consists of everything else, above such core technologies as HTTP, URI/IRIs, DOM, XML, Unicode, and ECMAScript; below presentation-layer technologies like CSS and the NPAPI; and to the side of technologies like Geolocation, SVG, MathML, and XHR."></p>
<!--START dev-html-->


element is available. For example, it is inappropriate to use a <code>canvas</code> element to
render a page heading: if the desired presentation of the heading is graphically intense, it
should be marked up using appropriate elements (typically <code>h1</code>) and then styled using
CSS and supporting technologies such as XBL.</p>
CSS and supporting technologies such as Web Components.</p>

<p>When authors use the <code>canvas</code> element, they must also provide content that, when
presented to the user, conveys essentially the same function or purpose as the
data-x="concept-appcache-init">application cache selection algorithm</span> with no manifest, and
passing in the <code>Document</code>.</p>

<!--CLEANUP-->
<p class="note">Because the processing of the <code data-x="attr-html-manifest">manifest</code>
attribute happens only once the root element is parsed, any URLs referenced by processing
instructions before the root element (such as <code data-x="">&lt;?xml-stylesheet?></code> and
<code data-x="">&lt;?xbl?></code> PIs) will be fetched from the network and cannot be
instructions before the root element (such as <code data-x="">&lt;?xml-stylesheet?></code> PIs) will be fetched from the network and cannot be
cached.</p><!-- v2: fix this somehow -->

<p>User agents may examine the namespace of the root <code>Element</code> node of this
parsing, the user agent must <span>update the session history with the new page</span>.</p>

<p>User agents may add content to the <code>head</code> element of the <code>Document</code>, e.g.
linking to a style sheet or an XBL binding, providing script, giving the document a
linking to a style sheet or a binding, providing script, giving the document a
<code>title</code>, etc.</p>

<p class="note">In particular, if the user agent supports the <code data-x="">Format=Flowed</code>
feature of RFC 3676 then the user agent would need to apply extra styling to cause the text to
wrap correctly and to handle the quoting feature. This could be performed using, e.g., an XBL
wrap correctly and to handle the quoting feature. This could be performed using, e.g., a
binding or a CSS extension.</p>

<p>The <span>task source</span> for the two tasks mentioned in this section must be the
fully loading, the user agent must <span>update the session history with the new page</span>.</p>

<p>User agents may add content to the <code>head</code> element of the <code>Document</code>, or
attributes to the element <var data-x="">host element</var>, e.g. to link to a style sheet or an
XBL binding, to provide a script, to give the document a <code>title</code>, to make the media
attributes to the element <var data-x="">host element</var>, e.g. to link to a style sheet or a
binding, to provide a script, to give the document a <code>title</code>, to make the media
<span data-x="attr-media-autoplay">autoplay</span>, etc.</p>


fully loading, the user agent must <span>update the session history with the new page</span>.</p>

<p>User agents may add content to the <code>head</code> element of the <code>Document</code>, or
attributes to the <code>embed</code> element, e.g. to link to a style sheet or an XBL binding, or
attributes to the <code>embed</code> element, e.g. to link to a style sheet or a binding, or
to give the document a <code>title</code>.</p>

<p class="note" id="sandboxPluginNavigate">If the <code>Document</code>'s <span>active sandboxing
data-x="">addEventListener()</code>, by explicit <span>event handler content attributes</span>, by
<span>event handler IDL attributes</span>, or otherwise.</li>

<li>Processing of technologies like XBL or SVG that have their own scripting features.</li>
<li>Processing of technologies like SVG that have their own scripting features.</li>

</ul>

input:not([type=image]), textarea { box-sizing: border-box; }</pre>

<p>Each kind of form control is also given a specific default binding, as described in subsequent
sections, which implements the look and feel of the control.</p>
sections, which implements the look and feel of the control.</p> <!-- a binding -->




<div class="impl">

<h3>Bindings</h3>
<h3>Bindings</h3> <!-- a binding -->

<h4>Introduction</h4>

0 comments on commit d92962f

Please sign in to comment.
You can’t perform that action at this time.