Closed
Bug 1439486
Opened 8 years ago
Closed 5 years ago
[wpt-sync] Sync PR 6596 - Restrict notifications to secure top-level contexts.
Categories
(Testing :: web-platform-tests, enhancement, P3)
Testing
web-platform-tests
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: wpt-sync, Unassigned)
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 6596 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/w3c/web-platform-tests/pull/6596
Details from upstream follow.
Dominick Ng wrote:
> Restrict notifications to secure top-level contexts.
>
> This change migrates the notifications tests to use HTTPS. It also adds
> new tests to ensure that permission cannot be requested from insecure or
> non-top-level contexts.
>
> This is in line with Google Chrome's move to block notifications permission from being requested in [insecure](https://www.chromestatus.com/feature/5759967025954816) and [non-top-level contexts](https://www.chromestatus.com/feature/6451284559265792) as of version 61. A change to the Notifications API spec will also be filed once these tests are accepted.
>
>
>
| Reporter | ||
Updated•8 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
| Reporter | ||
Updated•8 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Reporter | ||
Updated•8 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
| Reporter | ||
Updated•8 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Reporter | ||
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•