Skip to content
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

Notifications API #534

Closed
3 tasks done
rejhgadellaa opened this issue Oct 4, 2023 · 2 comments
Closed
3 tasks done

Notifications API #534

rejhgadellaa opened this issue Oct 4, 2023 · 2 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@rejhgadellaa
Copy link

Description

The Notifications API allows web pages to control the display of system notifications to the end user. These are outside the top-level browsing context viewport, so therefore can be displayed even when the user has switched tabs or moved to a different app. The API is designed to be compatible with existing notification systems, across different platforms.
MDN - Notification API

While all major browser engines now support the Notification API (and related API's like Web Push, etcetera), there remain a lot of unsupported features.

Also, I know for a fact that Safari acts like it supports certain features, but they actually don't do anything. For example:

  • ServiceWorkerRegistration.showNotification() would return a Promise that resolves to a list, but the list would always be empty. Note: Safari 17 now behaves correctly, but previous versions did not
  • Notification.close() does not throw an error, but it doesn't do anything.

Beside these "no-ops", I would love to see support for actions, image, renotify, requireInteraction, silent, etcetera, in all major browsers.

Specification

https://notifications.spec.whatwg.org/

Open Issues

No response

Tests

https://wpt.fyi/results/notifications

Current Implementations

  • Blink
  • Gecko
  • WebKit

Standards Positions

No response

Browser bug reports

No response

Developer discussions

No response

Polls & Surveys

No response

Existing Usage

https://chromestatus.com/metrics/feature/timeline/popularity/371

Workarounds

No response

Accessibility Impact

No response

Privacy Impact

No response

Other

No response

@rejhgadellaa rejhgadellaa added the focus-area-proposal Focus Area Proposal label Oct 4, 2023
@rejhgadellaa rejhgadellaa changed the title Notification API Notifications API Oct 4, 2023
@foolip
Copy link
Member

foolip commented Oct 6, 2023

Looking at https://wpt.fyi/results/notifications, it looks like the tests don't cover requireInteraction and some other things mentioned. https://github.com/web-platform-tests/wpt/tree/master/notifications has a bunch of manual tests, including for requireInteraction.

I think that in order to produce a score for this feature, either we'd to automate those tests (is that tractable?) or find a way to consider manual tests.

@nairnandu
Copy link
Contributor

Thank you for proposing Notifications API for inclusion in Interop 2024.

We wanted to let you know that this proposal was not selected to be part of Interop 2024. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year, if necessary.

For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024!

Posted on behalf of the Interop team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus-area-proposal Focus Area Proposal
Projects
Status: Done
Development

No branches or pull requests

3 participants