安全上下文
此特征只可用于 安全上下文 (HTTPS)，在某些或所有 支持浏览器 .

注意： This feature is not available in SharedWorker

注意 : Safari still uses the callback syntax to get the permission. Read Using the Notifications API for a good example of how to feature detect this and run code as appropriate.

requestPermission() 方法在 Notification interface requests permission from the user for the current origin to display notifications.

句法

The latest spec has updated this method to a promise-based syntax that works like this:

Notification.requestPermission().then(function(permission) { ... });
					

Previously, the syntax was based on a simple callback; this version is now deprecated:

Notification.requestPermission(callback);
					

参数

callback 可选 Deprecated since Gecko 46

An optional callback function that is called with the permission value. Deprecated in favor of the promise return value.

返回

A Promise 解析为 DOMString with the permission picked by the user. Possible values for this string are:

• granted
• denied
• default

范例

Assume this basic HTML:

<button onclick="notifyMe()">Notify me!</button>
					

It's possible to send a notification as follows — here we present a fairly verbose and complete set of code you could use if you wanted to first check whether notifications are supported, then check if permission has been granted for the current origin to send notifications, then request permission if required, before then sending a notification.

function notifyMe() {
  // Let's check if the browser supports notifications
  if (!("Notification" in window)) {
    alert("This browser does not support desktop notification");
  }
  // Let's check whether notification permissions have already been granted
  else if (Notification.permission === "granted") {
    // If it's okay let's create a notification
    var notification = new Notification("Hi there!");
  }
  // Otherwise, we need to ask the user for permission
  else if (Notification.permission !== "denied") {
    Notification.requestPermission().then(function (permission) {
      // If the user accepts, let's create a notification
      if (permission === "granted") {
        var notification = new Notification("Hi there!");
      }
    });
  }
  // At last, if the user has denied notifications, and you
  // want to be respectful there is no need to bother them any more.
}
					

We no longer show a live sample on this page, as Chrome and Firefox no longer allow notification permissions to be requested from cross-origin <iframe> s, with other browsers to follow. To see a example in action, check out our To-do list example (also see the app running live )。

注意 : In the above example we spawn notifications in response to a user gesture (clicking a button). This is not only best practice — you should not be spamming users with notifications they didn't agree to — but going forward browsers will explicitly disallow notifications not triggered in response to a user gesture. Firefox is already doing this from version 72, for example.

规范

规范	状态	注释
Notifications API	实时标准	Living standard

浏览器兼容性

The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request. 更新 GitHub 上的兼容性数据

	桌面						移动
	Chrome	Edge	Firefox	Internet Explorer	Opera	Safari	Android webview	Chrome for Android	Firefox for Android	Opera for Android	Safari on iOS	Samsung Internet
requestPermission	Chrome 46	Edge 14	Firefox 47 47 From Firefox 70 onwards, cannot be called from a cross-origin IFrame. From Firefox 72 onwards, can only be called in response to a user gesture such as a click 事件。	IE No	Opera 40	Safari Yes	WebView Android No	Chrome Android 46	Firefox Android Yes	Opera Android 41	Safari iOS No	Samsung Internet Android 5.0

图例

完整支持

完整支持

不支持

不支持

见实现注意事项。

另请参阅

• Using the Notifications API

元数据

• 最后修改： Jul 23, 2020