On Wed, Dec 15, 2010 at 3:42 AM, Jonas Sicking jo...@sicking.cc wrote:
Speaking of which, we use UNKNOWN_ERR for a bunch of other
internal consistency issues. Is this OK by everyone, should we use
another,
or should we create a new one? (Ideally these issues will be few and far
between
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf Of Jeremy Orlow
Sent: Friday, December 10, 2010 5:03 AM
I noticed that QUOTA_ERR is commented out. I can't remember when or why and
the blame history is a bit mangled. Does anyone else? In Chromium we
On Wed, Dec 15, 2010 at 12:08 AM, Pablo Castro
pablo.cas...@microsoft.comwrote:
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org]
On Behalf Of Jeremy Orlow
Sent: Friday, December 10, 2010 5:03 AM
I noticed that QUOTA_ERR is commented out. I can't remember when or
On 12/14/2010 4:16 PM, Jeremy Orlow wrote:
Shawn said NOT_FOUND_ERR. NOT_ALLOWED_ERR seems slightly better to me.
Shawn, what do you think?
I don't have a strong opinion either way.
Cheers,
Shawn
smime.p7s
Description: S/MIME Cryptographic Signature
I was confused re not overlapping with other exception codes. As long as we
don't have overlap within this particular exception type, we're OK.
I noticed that QUOTA_ERR is commented out. I can't remember when or why and
the blame history is a bit mangled. Does anyone else? In Chromium we
On 12/10/2010 5:03 AM, Jeremy Orlow wrote:
Speaking of which, we use UNKNOWN_ERR for a bunch of other
internal consistency issues. Is this OK by everyone, should we use another,
or should we create a new one? (Ideally these issues will be few and far
between as we make things more robust.)
On Fri, Dec 10, 2010 at 6:01 PM, Shawn Wilsher sdwi...@mozilla.com wrote:
On 12/10/2010 5:03 AM, Jeremy Orlow wrote:
Speaking of which, we use UNKNOWN_ERR for a bunch of other
internal consistency issues. Is this OK by everyone, should we use
another,
or should we create a new one?
