[html5] r4479 - [e] (0) Avoid requiring that the user be notified of something, since that's a U [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 5 00:11:09 PST 2010
Author: ianh
Date: 2010-01-05 00:11:05 -0800 (Tue, 05 Jan 2010)
New Revision: 4479
Modified:
complete.html
index
source
Log:
[e] (0) Avoid requiring that the user be notified of something, since that's a UI issue.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8325
Modified: complete.html
===================================================================
--- complete.html 2010-01-05 08:06:37 UTC (rev 4478)
+++ complete.html 2010-01-05 08:11:05 UTC (rev 4479)
@@ -51510,7 +51510,7 @@
<a href=#report-the-error>report the error</a> using the <code title=handler-window-onerror><a href=#handler-window-onerror>onerror</a></code> <a href=#event-handlers title="event
handlers">event handler</a> of the <a href="#script's-global-object">script's global
object</a>. If the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> after this, then
- the error should be reported to the user.</p>
+ the error may be reported to the user.</p>
<hr><p>When the user agent is required to <dfn id=report-the-error title="report the
error">report an error</dfn> <var title="">error</var> using the
@@ -51533,7 +51533,7 @@
<i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i>.</p>
<p>Any uncaught exceptions thrown or errors caused by this
- function must be reported to the user immediately after the error
+ function may be reported to the user immediately after the error
that the function was called for, without using the <a href=#report-the-error title="report the error">report an error</a> algorithm
again.</p>
@@ -63680,7 +63680,7 @@
<p>For shared workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> afterwards, or if
the error occurred while handling a previous script error, the error
- should be reported to the user.
+ may be reported to the user.
</p>
<p>For dedicated workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> afterwards, or if
@@ -63698,7 +63698,7 @@
that worker is also a dedicated worker, then the user agent must
again <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-worker-error-event>fire a worker error
event</a> at the <code><a href=#worker>Worker</a></code> object associated with
- <em>that</em> worker. Otherwise, then the error should be reported
+ <em>that</em> worker. Otherwise, then the error may be reported
to the user.</p>
<p>The <a href=#task-source>task source</a> for the tasks mentioned above is the
Modified: index
===================================================================
--- index 2010-01-05 08:06:37 UTC (rev 4478)
+++ index 2010-01-05 08:11:05 UTC (rev 4479)
@@ -48675,7 +48675,7 @@
<a href=#report-the-error>report the error</a> using the <code title=handler-window-onerror><a href=#handler-window-onerror>onerror</a></code> <a href=#event-handlers title="event
handlers">event handler</a> of the <a href="#script's-global-object">script's global
object</a>. If the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> after this, then
- the error should be reported to the user.</p>
+ the error may be reported to the user.</p>
<hr><p>When the user agent is required to <dfn id=report-the-error title="report the
error">report an error</dfn> <var title="">error</var> using the
@@ -48698,7 +48698,7 @@
<i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i>.</p>
<p>Any uncaught exceptions thrown or errors caused by this
- function must be reported to the user immediately after the error
+ function may be reported to the user immediately after the error
that the function was called for, without using the <a href=#report-the-error title="report the error">report an error</a> algorithm
again.</p>
Modified: source
===================================================================
--- source 2010-01-05 08:06:37 UTC (rev 4478)
+++ source 2010-01-05 08:11:05 UTC (rev 4479)
@@ -58004,7 +58004,7 @@
handlers">event handler</span> of the <span>script's global
object</span>. If the error is still <i
title="concept-error-nothandled">not handled</i> after this, then
- the error should be reported to the user.</p>
+ the error may be reported to the user.</p>
<hr>
@@ -58035,7 +58035,7 @@
<i title="concept-error-nothandled">not handled</i>.</p>
<p>Any uncaught exceptions thrown or errors caused by this
- function must be reported to the user immediately after the error
+ function may be reported to the user immediately after the error
that the function was called for, without using the <span
title="report the error">report an error</span> algorithm
again.</p>
@@ -72575,7 +72575,7 @@
<p>For shared workers, if the error is still <i
title="concept-error-nothandled">not handled</i> afterwards, or if
the error occurred while handling a previous script error, the error
- should be reported to the user.
+ may be reported to the user.
<!--END complete-->
<a href="#refsHTML5">[HTML5]</a>
<!--START complete-->
@@ -72601,7 +72601,7 @@
that worker is also a dedicated worker, then the user agent must
again <span>queue a task</span> to <span>fire a worker error
event</span> at the <code>Worker</code> object associated with
- <em>that</em> worker. Otherwise, then the error should be reported
+ <em>that</em> worker. Otherwise, then the error may be reported
to the user.</p>
<p>The <span>task source</span> for the tasks mentioned above is the
More information about the Commit-Watchers
mailing list