From 55014d89019c5c198c659a837d2ead48dca7fb06 Mon Sep 17 00:00:00 2001
From: Daniel Vogelheim Draft Community Group Report,
- HTML elements to request browser permissions in-page. This specifies a set of new HTML elements, whose common goal is to provide
users with a way to control browser permissions and the associated
@@ -789,7 +789,7 @@
This specification was published by the Web Platform Incubator Community Group.
@@ -806,8 +806,8 @@ The HTML Permission Elements
+ The HTML Permission Elements
The HTML Permission Elements
The HTML Permission Elements
Abstract
+ Abstract
Status of this document
+ Status of this document
isValid — query whether the element can currently be activated.
- invalidReason — return a string representation of why the element currently cannot be activated.
- onpromptdismiss — notifies when the user has dismissed a permission prompt that resulted from an interaction with the element
- onpromptaction — notifies when a permission prompt that resulted from an interaction with the element has been answered by the user (positively or negatively).
- onvalidationstatuschange — notifies when the validation status changes.
- interface mixin { -InPagePermissionMixin readonly attribute boolean isValid ; -readonly attribute InPagePermissionMixinBlockerReason invalidReason ; +The
+InPagePermissionMixininterface mixin is defined as follows:+interface mixin { +InPagePermissionMixin readonly attribute boolean isValid ; +readonly attribute InPagePermissionMixinBlockerReason invalidReason ;readonly attribute PermissionState initialPermissionStatus ;readonly attribute PermissionState permissionStatus ; @@ -912,6 +902,19 @@
EventHandler ; };onvalidationstatuschange Elements using this mixin are expected to support the following +Content attributes:
+
isValid
+ invalidReason
+ onpromptdismiss
+ onpromptaction
+ onvalidationstatuschange
+ The isValid attribute reflects whether a the
permission element is not currently blocked.
tabindex content attribute on the
element is 0.
- The following are the event handlers (and their corresponding event handler event types) that must be supported on elements that include the InPagePermissionMixin:
+
The following are the event handlers (and their corresponding event handler event types) that must be supported on elements that include the InPagePermissionMixin:
geolocation element internal stateThe geolocation element uses all the internal slots from the InPagePermissionMixin, described in § 2.1 Mixin internal state. Additionally,
+
The geolocation element uses all the internal slots from the InPagePermissionMixin, described in § 2.1 Mixin internal state. Additionally,
geolocation has the following internal slots:
interface mixin { +InPagePermissionMixin IDL Index
+-interface mixin {InPagePermissionMixin readonly attribute boolean isValid ;readonly attribute InPagePermissionMixinBlockerReason invalidReason ;readonly attribute PermissionState initialPermissionStatus ; @@ -3010,7 +3013,7 @@I
HTMLGeolocationElement includes InPagePermissionMixin ;Issues Index
+Issues Index
There isn’t much precedence for describing the user agent UI in detail. It may be better to leave more freedom to user agents. ↵@@ -3277,7 +3280,7 @@