[Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681

--- Comment #12 from Joshua Bell <jsbell@chromium.org> ---
I have gone in and removed the "legacy" exception tables, replacing them with
prose. In nearly all cases this was simply mechanically turning this:

 <dl>
   <dt>FooError
   <dd>Condition
 </dl>

Into this:

 <p>
   If condition, throw a DOMException of type FooError.
 </p>

https://dvcs.w3.org/hg/IndexedDB/rev/7648f0c71309

This does NOT define an ordering, i.e. the methods are not stated
algorithmically, so there should be no normative change, and it means there's
no state change for this issue.

I also didn't re-order the exceptions to be first, so some of the methods read
like:

| Overview of method.
|
| If condition1 throw exception1.
| 
| Start of method description.
|
| If condition2 throw exception2.
|
| More of description.
|
| If condition3 throw exception3.

This funky ordering isn't new, but may be more obvious now. I can do a second
pass to move all the exception conditions to the start of each method.

I also standardized (for ease of later cleanup) on the grotesque wording:

  If <condition>, 
  the implementation MUST throw a DOMException of type FooError.

Per http://dom.spec.whatwg.org/#exception-domexception this could be more
succinctly stated as simply:

  If <condition>, throw a "FooError".

... but that wording clashes with the non-algorithmic description of the
methods, and implies an ordering.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 18 April 2013 21:51:24 UTC