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

[Bug 21740] Guidance on DOMError and promises

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Nov 2013 22:46:45 +0000
To: public-script-coord@w3.org
Message-ID: <bug-21740-3890-XS3KuIRDSk@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21740

Arun <arun@mozilla.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arun@mozilla.com

--- Comment #4 from Arun <arun@mozilla.com> ---
Actually, I'm not sure I agree with Comment 3.  Why not use DOMError with the
reject path of a Promise?  It allows implementations to encapsulate meaningful
errors, so that within the reject path, you can take action.  

If the counsel is to throw instead with DOMException, then that creates more
try-catch style code, which, alongside Promises, is a bit of a pain.

So this brings me back to my first question: why not use DOMError?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 15 November 2013 22:46:46 UTC

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