Closed
Bug 1004112
Opened 10 years ago
Closed 10 years ago
Feature Detection API Sensible Defaults
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
2.0 S1 (9may)
People
(Reporter: curtisk, Unassigned)
References
Details
(Whiteboard: [privacy])
Use of the API may be allowable by a single user choice for privileged apps (such as marketplace) but should more granular notification should be considered for apps of lower privelage.
![]() |
Reporter | |
Updated•10 years ago
|
Whiteboard: [privacy]
Comment 1•10 years ago
|
||
I honestly have a hard time understanding comment 0. Would you mind clarifying please, Curtis? Thanks!
Flags: needinfo?(curtisk)
![]() |
Reporter | |
Comment 2•10 years ago
|
||
Sure. I'm saying that by default it may be fine for the user to consent for the Marketplace app to use the feature detection API on first run and to have some mechanism to disable said decision say in the settings menu somewhere if they change their mind. Same may be true for packaged apps the user has installed that need or want access to the information. But that less privileged apps such as web apps or content pages should have to ask every time use of the api is desired so the user can decide if they want to allow the access or not. I am looking for clarification and documentation on how various things can request access to the information and what the default settings may be for such a request.
Flags: needinfo?(curtisk)
Comment 3•10 years ago
|
||
This is only intended for privileged apps for now. Does that answer the concern in comment 2?
![]() |
Reporter | |
Comment 4•10 years ago
|
||
(In reply to :Ehsan Akhgari (lagging on bugmail, needinfo? me!) from comment #3) > This is only intended for privileged apps for now. Does that answer the > concern in comment 2? For privileged / reviewed apps I think this will be fine. If we change the access we'll have to revisit this.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Target Milestone: --- → 2.0 S1 (9may)
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•