- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 28 May 2014 12:29:29 +0200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "www-style@w3.org" <www-style@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>
On Tue, May 27, 2014 at 9:42 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Tue, May 27, 2014 at 12:35 AM, Anne van Kesteren <annevk@annevk.nl> wrote: >> Well, you're changing the status but can that actually be observed >> somehow? If not, why are you changing the status? Changing the status >> of something and making that observable typically requires queuing a >> task, unless you use a promise, but in that case you can only change >> the status once, by resolving the promise. > > I'm not sure what you're talking about here, so I've pinged you on > IRC. Hopefully we can resolve it better there. Okay. If people want to follow along, http://krijnhoetmer.nl/irc-logs/whatwg/20140527#l-668 and http://krijnhoetmer.nl/irc-logs/whatwg/20140528 >> Well, you could look at how http://dom.spec.whatwg.org/#concept-throw >> does it... > > I was specifically looking for something other than "remember to check > this specific spec to see how it does it". ^_^ Like, CSS puts some > spec-authoring guidance on its wiki > <http://wiki.csswg.org/spec#coordination-between-specifications>. > Something similar (even in our wiki - if you don't have an account, > just send me some guidance and I can add it myself) would be great. Well, DOM defines DOMException at the moment so it would be *the* specification to check for usage. And in particular what I pointed you to is exactly what you want to do here. Reject with a DOMException object whose name is x, message is some user agent-defined value, and code is set per the table. >> In due course this should be integrated into IDL at which >> point it hopefully provides the proper wording for both normal members >> and promise returning members. > > Not sure how IDL would help, since this is prose text throwing the exception. The plan is for IDL to define the platform error/exception story and have simple hooks for rejecting a promise with an error/exception of sorts and throwing an error/exception of sorts. Similar to how DOM provides a simple hook for throwing a DOMException today. https://www.w3.org/Bugs/Public/show_bug.cgi?id=23367 -- http://annevankesteren.nl/
Received on Wednesday, 28 May 2014 10:29:59 UTC