W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

[Bug 26517] Methods that return promises are unable to throw exceptions

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Oct 2014 16:19:06 +0000
To: public-script-coord@w3.org
Message-ID: <bug-26517-3890-FOEak7fN4n@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26517

Joshua Bell <jsbell@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsbell@google.com

--- Comment #21 from Joshua Bell <jsbell@google.com> ---
(In reply to Olli Pettay from comment #20)
> This inconsistency in rather horrible. 

And yet, we received exactly that complaint from Indexed DB users who ran into
that issue with an API that works the way you propose (both synchronous and
asynchronous failures):

var request = store.put(userdata, key);
request.onsuccess = ...;
request.onerror = ...;

"What do you mean I *also* need to catch exceptions from put() if the userdata
is something that can't be cloned? I already have an error handler - make it
consistent!"

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 7 October 2014 16:19:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC