Closed Bug 810112 Opened 12 years ago Closed 11 years ago

Reset permission when permission rationale changes

Categories

(Core Graveyard :: DOM: Apps, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED WORKSFORME
blocking-basecamp -

People

(Reporter: ladamski, Assigned: ddahl)

References

Details

When the rationale for a permission changes, we should reset the permission bit to re-ask the user. I don't feel this blocks basecamp, but nom'ing to get a sanity check.
To clarify, this should only happen for explicit permissions. Yes, would require keep looking for string changes during updates.
Assignee: nobody → ddahl
blocking-basecamp: ? → -
Is this still an issue?
I think that updating an app triggers the permission installation code which resets old permissions.
(In reply to Gregor Wagner [:gwagner] from comment #3) > I think that updating an app triggers the permission installation code which > resets old permissions. So, do we need to do anything (listen for events that affect permissions, etc) in between when an app is installed and when an app is updated? Or can we close this as INVALID?
The use-case mentioned in the Description should work and I think we can close this bug. Jason, have you tested this scenario? We do have a problem when we update an app when it's running but I guess that should be a another bug. Everything should work fine after we restart the app.
Flags: needinfo?(jsmith)
Yes. See bug 833633 that describes this behavior that exists today. Given that we are always resetting the permission right now, we can close this out as works for me. When we decide to fix bug 833633 however, we should make sure to handle the special case cited in this bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(jsmith)
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.