Esta traducción está incompleta. Por favor, ayuda a traducir este artículo del inglés.
This is an experimental technology
Because this technology's specification has not stabilized, check the compatibility table for the proper prefixes to use in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the spec changes.
La propiedad icon indica la URL del icono a usar dentro de la notificacion.
var icon = instanceOfNotification.icon;
String que representa una URL válida.
|Web Notifications||Working Draft||Initial specification.|
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari|
|Basic support||5 webkit (see notes)
|4.0 moz (see notes)
|Not supported||25||6 (see notes)|
|Feature||Android||Firefox Mobile (Gecko)||Firefox OS||IE Mobile||Opera Mobile||Safari Mobile|
|Basic support||?||4.0 moz (see notes)
|1.0.1 moz (see notes)
|Not supported||?||Not supported|
- Prior to Firefox 22 (Firefox OS <1.2), the instantiation of a new notification must be done with the
navigator.mozNotificationobject through its
- Prior to Firefox 22 (Firefox OS <1.2), the Notification was displayed when calling the
showmethod and was supporting the
- Nick Desaulniers has written a Notification shim to cover both newer and older implementations.
- One particular Firefox OS issue is that you can pass a path to an icon to use in the notification, but if the app is packaged you cannot use a relative path like
/my_icon.png. You also can't use
window.location.origin + "/my_icon.png"because
window.location.originis null in packaged apps. The manifest origin field fixes this, but it is only available in Firefox OS 1.1+. A potential solution for supporting Firefox OS <1.1 is to pass an absolute URL to an externally hosted version of the icon. This is less than ideal as the notification is displayed immediately with the icon missing, then the icon is fetched, but it works on all versions of Firefox OS.
- Prior to Chrome 22, the support for notification was following an old prefixed version of the specification and was using the
navigator.webkitNotificationsobject to instantiate a new notification.
- Prior to Chrome 32,
Notification.permissionwas not supported.
- Safari started supporting notification with Safari 6 but only on Mac OSX 10.8+ (Mountain Lion).