[html5] r3295 - [] (0) Define handling of <area>.click() and popup blockers.

whatwg at whatwg.org whatwg at whatwg.org
Tue Jun 16 21:44:22 PDT 2009


Author: ianh
Date: 2009-06-16 21:44:20 -0700 (Tue, 16 Jun 2009)
New Revision: 3295

Modified:
   index
   source
Log:
[] (0) Define handling of <area>.click() and popup blockers.

Modified: index
===================================================================
--- index	2009-06-17 04:29:50 UTC (rev 3294)
+++ index	2009-06-17 04:44:20 UTC (rev 3295)
@@ -25104,10 +25104,14 @@
   <p>The <a href=#activation-behavior>activation behavior</a> of <code><a href=#the-area-element>area</a></code>
   elements is to run the following steps:</p>
 
-  <ol><li>If the <code title=event-DOMActivate>DOMActivate</code> event
-   in question is not <span title=concept-events-trusted>trusted</span> (i.e. a <code title=dom-click><a href=#dom-click>click()</a></code> method call was the reason for the
-   event being dispatched), and the <code><a href=#the-area-element>area</a></code> element's <code title=attr-area-target>target</code> attribute is <span class=XXX>...</span> then raise an
-   <code><a href=#invalid_access_err>INVALID_ACCESS_ERR</a></code> exception.</li>
+  <ol><li><p>If the <code title=event-DOMActivate>DOMActivate</code>
+   event in question is not <span title=concept-events-trusted>trusted</span> (i.e. a <code title=dom-click><a href=#dom-click>click()</a></code> method call was the reason for the
+   event being dispatched), and the <code><a href=#the-area-element>area</a></code> element's <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code> attribute is such that
+   applying <a href=#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-name>the rules for choosing a browsing context given a
+   browsing context name</a>, using the value of the <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code> attribute as the
+   browsing context name, would result in there not being a chosen
+   browsing context, then raise an <code><a href=#invalid_access_err>INVALID_ACCESS_ERR</a></code>
+   exception and abort these steps.</li>
 
    <li>Otherwise, the user agent must <a href=#following-hyperlinks title="following
    hyperlinks">follow the hyperlink</a> defined by the

Modified: source
===================================================================
--- source	2009-06-17 04:29:50 UTC (rev 3294)
+++ source	2009-06-17 04:44:20 UTC (rev 3295)
@@ -27529,14 +27529,18 @@
 
   <ol>
 
-   <li>If the <code title="event-DOMActivate">DOMActivate</code> event
-   in question is not <span
+   <li><p>If the <code title="event-DOMActivate">DOMActivate</code>
+   event in question is not <span
    title="concept-events-trusted">trusted</span> (i.e. a <code
    title="dom-click">click()</code> method call was the reason for the
    event being dispatched), and the <code>area</code> element's <code
-   title="attr-area-target">target</code> attribute is <span
-   class="XXX">...</span> then raise an
-   <code>INVALID_ACCESS_ERR</code> exception.</li>
+   title="attr-hyperlink-target">target</code> attribute is such that
+   applying <span>the rules for choosing a browsing context given a
+   browsing context name</span>, using the value of the <code
+   title="attr-hyperlink-target">target</code> attribute as the
+   browsing context name, would result in there not being a chosen
+   browsing context, then raise an <code>INVALID_ACCESS_ERR</code>
+   exception and abort these steps.</p></li>
 
    <li>Otherwise, the user agent must <span title="following
    hyperlinks">follow the hyperlink</span> defined by the




More information about the Commit-Watchers mailing list