-
Notifications
You must be signed in to change notification settings - Fork 49
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
Get rid of entry settings object usage #168
Conversation
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.
Statics are problematic
notifications.bs
Outdated
@@ -718,7 +722,7 @@ constructor steps are: | |||
<h3 id=static-members>Static members</h3> | |||
|
|||
<p>The static <dfn attribute for=Notification><code>permission</code></dfn> getter steps are to | |||
return the <a>permission</a> for the <a>entry settings object</a>'s | |||
return the <a>permission</a> for <a>this</a>'s <a>relevant settings object</a>'s |
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.
This is static so it doesn't work. You want the <a>current settings object</a>
.
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.
Hmm this probably is preexisting in requestPermission() somehow.
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 fixed both, thanks for spotting that!
Use the relevant settings object instead. Fixes #86.
New commit message:
|
Use the relevant settings object instead.
Fixes #86.
(Note that this builds upon #167.)
Preview | Diff