- From: <bugzilla@jessica.w3.org>
- Date: Fri, 29 Aug 2014 00:51:16 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26517 --- Comment #19 from Yutaka Hirano <yhirano@google.com> --- IMO I prefer the current spec - returning a rejected Promise rather than throwing an error. By the way, many APIs are currently using Promises. Chrome already returns a rejected Promise from APIs returning a Promise when there is an error, although the implementation is not perfect yet (see https://code.google.com/p/chromium/issues/detail?id=359386). Changing the draft will affect many APIs (we thought that part of them for example WebCrypto were stable and "shipped" them). It would be great if we conclude this discussion soon. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Friday, 29 August 2014 00:51:18 UTC