-
Notifications
You must be signed in to change notification settings - Fork 29
Use SecurityError for document state check #143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Blocked on tests and updating implementations. |
|
@samuelgoto, you ok with this change? If yes, I'll make them also in WebKit. |
Sounds reasonable to me to be more specific than |
samuelgoto
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel strongly about this, seems like a reasonable differentiation between errors.
We currently have an over-reliance on NotAllowedError (particularly in Cred Man). This makes things a bit more distinguishable (for interop testing), and lets developers know a bit more about what's going on.
The following tasks have been completed:
Implementation commitment:
Documentation and checks
Preview | Diff