New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 611340 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Use NotAllowedError instead of defining a new PermissionDeniedError

Project Member Reported by mvanouwe...@chromium.org, May 12 2016

Issue description

To follow this spec change: https://github.com/w3c/push-api/pull/192
 

Comment 1 by peter@chromium.org, May 12 2016

Cc: mscales@chromium.org mattgaunt@chromium.org
We have been firing the PermissionDeniedError exception from the start, are we completely confident it's fine to change this? A quick search on Google and GitHub tell me it probably is— the only references I can find are the Gecko and Blink tests, but maybe Mat/Matt knows about other usage?
I'm not aware of anyone relying on this, although as with any change I'm sure some people will get broken, but if all browsers are going to implment this, change sooner rather than later is better. I'm assuming this change is to make the error throwable based on different issues rather than just when the user denies the permission? If not, why change, because this error is harder to understand at first glance.
I think mlamouri added it for a non-permission related case in the presentation api.
Owner: harkness@chromium.org
Status: Assigned (was: Available)

Comment 5 by peter@chromium.org, Aug 2 2016

Owner: peter@chromium.org
Mozilla uses a NotAllowedError as well now, so let's match the spec.

[1] https://github.com/mozilla/gecko-dev/blob/cb4337c62c0b60b93d118e7cb5b769a2a2386703/dom/base/domerr.msg#L156

Comment 7 by peter@chromium.org, Aug 4 2016

Labels: M-54
Status: Fixed (was: Assigned)

Sign in to add a comment