Bug 1371741 Comment 21 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Let me know when you have a new patch up, or I can take this if you want.

Note that there have been some changes in this area, both in our code and the spec. e.g. the spec no longer mentions throwing SecurityError anywhere.

We should probably reject with NotAllowedError (and the unrelated existing "not fully active" SecurityError should be InvalidStateError now according to the spec) [1].
Revision 1 by
on 
Let me know when you have a new patch up, or I can take this if you want.

Note that there have been some changes in this area, both in our code and the spec. e.g. the spec no longer mentions throwing SecurityError anywhere.

We should probably reject with NotAllowedError (and the adjacent "not fully active" SecurityError should be InvalidStateError now according to the spec) [1].
Revision 2 by
on 
Let me know when you have a new patch up, or I can take this if you want.

Note that there have been some changes in this area, both in our code and the spec. e.g. the spec no longer mentions throwing SecurityError anywhere.

We should probably reject with NotAllowedError (and the adjacent SecurityErrors should probably either be NotAllowedError or InvalidStateError now according to the spec, not sure which one to pick since they're a bit edge-casy) [1].

Back to Bug 1371741 Comment 21