Closed Bug 815505 Opened 12 years ago Closed 12 years ago

[Settings] Installing an app that specifies a large amount of permissions - one permission is listed empty in app permissions

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

RESOLVED WONTFIX
B2G C2 (20nov-10dec)
blocking-basecamp +

People

(Reporter: jsmith, Assigned: Margaret)

Details

(Keywords: late-l10n)

Attachments

(1 file, 1 obsolete file)

Attached image Missing Permission
Build: Device - Unagi Hashes <project name="gaia" path="gaia" remote="b2g" revision="176aea9cba4965594350f282751758b14d2624fc"/> <project name="releases/gecko" path="gecko" remote="mozillaorg" revision="4eaacd3fad7b6da220de206c0013dc0f307455c9"/> Steps: 1. Install the web app from http://people.mozilla.com/~fdesre/openwebapps/test.html listed install app with permissions 2. Go to settings --> app permissions --> that app in particular 3. Scroll down the list of permissions Expected: All permissions called out in the permissions property in the manifest should be listed with the correct default permission levels. Actual: See attached screenshot. There's a permission getting listed here that's blank.
Blocking nom - listing permissions in the app permissions UI without a name is problematic, as the user has the ability to modify a permission without knowing what they are modifying.
blocking-basecamp: --- → ?
Jason, do you know what permission is the blank one here and how common that one will be used? I agree this is an issue and we shouldn't have blank lines here.
Looks like the permissions missing here are: - network-events - background-sensors Don't know which one of these is the blank one. Don't know how common either. Jonas - how often would we expect these permissions to be used by a hosted app?
Flags: needinfo?(jonas)
Assignee: nobody → etienne
blocking-basecamp: ? → +
Priority: -- → P1
Target Milestone: --- → B2G C2 (20nov-10dec)
Missing l10n key, assigning :stas. Feel free to redirect if needed.
Assignee: etienne → stas
Keywords: late-l10n
Assignee: stas → nobody
Following what Jason said in comment 3, I found the network-events entity name was wrong, and that we were missing the background-sensors entity completely. I don't know if it matters where in the list I added 'background-sensors', also if "Background sensors" is the string we want. I'll cc lco to ask.
Assignee: nobody → margaret.leibovic
Attachment #686362 - Flags: review?(stas)
lco, see my last comment. Is "Background sensors" the string we want to use for the background-sensors permission, and is there specific any place in the list of app permissions where you'd like to see it?
Also, Jason, do you know of a list somewhere of all the permissions an app can have? We should verify that these are all in here: https://mxr.mozilla.org/gaia/source/apps/settings/js/apps.js#10 (Also, aw yeah! MXR!)
(In reply to Margaret Leibovic [:margaret] from comment #7) > Also, Jason, do you know of a list somewhere of all the permissions an app > can have? We should verify that these are all in here: > https://mxr.mozilla.org/gaia/source/apps/settings/js/apps.js#10 > > (Also, aw yeah! MXR!) I was about to suggest using https://developer.mozilla.org/en-US/docs/Apps/Manifest#permissions but apparently after looking at that code, there's much more undocumented permission properties. Hmm...Jonas do you know the full list?
(In reply to Jason Smith [:jsmith] from comment #3) > Looks like the permissions missing here are: > > - network-events > - background-sensors > > Don't know which one of these is the blank one. Don't know how common either. > > Jonas - how often would we expect these permissions to be used by a hosted > app? Neither of these permissions should be usable by hosted apps. Or non-privileged packaged apps. Network-events should only be permitted to certified apps.
Flags: needinfo?(jonas)
(In reply to Jonas Sicking (:sicking) from comment #9) > (In reply to Jason Smith [:jsmith] from comment #3) > > Looks like the permissions missing here are: > > > > - network-events > > - background-sensors > > > > Don't know which one of these is the blank one. Don't know how common either. > > > > Jonas - how often would we expect these permissions to be used by a hosted > > app? > > Neither of these permissions should be usable by hosted apps. Or > non-privileged packaged apps. Network-events should only be permitted to > certified apps. *email thread coming about this btw* Sounds like the right patch to do here is that we should only call out permissions in that patch that make sense to be shown and be modified. If it doesn't make sense, we shouldn't show it.
After hearing the discussions in IRC and threads, I'm going to suggest closing this bug for now for the one off and opening a new bug to track harmonizing the permissions referenced for the settings app against the result of bug 815565 + clear input on what an end-user is actually allow to see and modify. Does that align with everyone else?
Talked with Margaret in IRC - she agrees - I'm going to close this then.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Attachment #686362 - Attachment is obsolete: true
Attachment #686362 - Flags: review?(stas)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: