Closed
Bug 1737750
Opened 4 years ago
Closed 4 years ago
Permissions: PermissionName is now PowerfulFeatureName
Categories
(Core :: Permission Manager, task, P5)
Core
Permission Manager
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: marcos, Unassigned)
References
(
URL
)
Details
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15
Steps to reproduce:
The PermissionName enum was renamed PowerfulFeatureName. This helps clarify some confusion with permissions policy having "permissions" for various things.
URL: See https://github.com/w3c/permission...
Component: Untriaged → DOM: Security
Product: Firefox → Core
Small refactor to reflect a name change in the spec.
See https://github.com/w3c/permissions/pull/286/
|
||
Updated•4 years ago
|
Component: DOM: Security → Permission Manager
|
||
Comment 2•4 years ago
|
||
The severity field is not set for this bug.
:timhuang, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(tihuang)
Setting as low priority... doesn't really have any severity. It's more of a refactor.
Severity: -- → N/A
Priority: -- → P5
|
||
Updated•4 years ago
|
Type: defect → task
Flags: needinfo?(tihuang)
|
||
Updated•4 years ago
|
Attachment #9247700 -
Attachment is obsolete: true
Spec now uses a DOMString but allows implementers to use an enum... so the current code is totally fine.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•