Closed
Bug 815572
Opened 12 years ago
Closed 12 years ago
Standardize the Bluetooth permissions name (bluetooth or mozBluetooth)
Categories
(Core :: DOM: Device Interfaces, defect, P2)
Tracking
()
People
(Reporter: pauljt, Assigned: gwagner)
References
Details
Attachments
(3 files)
The bluetooth code has the permissions "mozBluetooth" but the PermissionsInstaller.jsm has both bluetooth and mozBluetooth.
"bluetooth" would be better imho since all other permissions and lowercase and unprefixed, but really I just need to know which is the "correct" one.
Comment 1•12 years ago
|
||
Nice catch! We're going to hook up the system message mechanism to the permission module and also confused about which one is actually preferred.
If we prefer "bluetooth" then we need to modify the permission check in BluetoothManager.cpp which is still using "mozBluetooth".
All the bluetooth-related apps seems supporting both "bluetooth" and "mozBluetooth".
Comment 2•12 years ago
|
||
(In reply to Gene Lian [:gene] from comment #1)
> Nice catch! We're going to hook up the system message mechanism to the
> permission module and also confused about which one is actually preferred.
>
> If we prefer "bluetooth" then we need to modify the permission check in
> BluetoothManager.cpp which is still using "mozBluetooth".
>
> All the bluetooth-related apps seems supporting both "bluetooth" and
> "mozBluetooth".
I'm o.k with the change. For Bluetooth module, like Gene mentioned, only one line in BluetoothManager.cpp needs to be modified.
Assignee | ||
Comment 3•12 years ago
|
||
The change is not hard but we have to be careful that we don't break anything. I made a couple of these changes already and the best thing to do is: add new permission to gaia, wait until it gets to all gaia branches, update the permission name in gecko, wait until we land the patch on all branches (including beta), remove old permission from gaia.
I think for bluetooth I already started landing the change on gaia a while back but I never finished landing the gecko change. So it's kind of my mistake that we have this mozBluetooth and bluetooth mess.
Assignee | ||
Comment 4•12 years ago
|
||
Lets change it. I checked the Gaia permissions and they all support mozBluetooth and bluetooth so we are good there.
Assignee: nobody → anygregor
Assignee | ||
Updated•12 years ago
|
blocking-basecamp: --- → ?
Assignee | ||
Updated•12 years ago
|
Attachment #685760 -
Flags: review?(kyle)
Updated•12 years ago
|
Attachment #685760 -
Flags: review?(kyle) → review+
Updated•12 years ago
|
blocking-basecamp: ? → +
Assignee | ||
Comment 5•12 years ago
|
||
Assignee | ||
Comment 6•12 years ago
|
||
This should land once we removed all the mozBluetooth permissions in Gaia.
Attachment #685773 -
Flags: review?(kyle)
Updated•12 years ago
|
Attachment #685773 -
Flags: review?(kyle) → review+
Assignee | ||
Updated•12 years ago
|
Whiteboard: leave-open
Assignee | ||
Comment 7•12 years ago
|
||
Attachment #685919 -
Flags: review?(jonas)
Assignee | ||
Comment 8•12 years ago
|
||
PR 6670 should only land after https://bug815572.bugzilla.mozilla.org/attachment.cgi?id=685760 is distributed to all trees.
Comment 9•12 years ago
|
||
Attachment #685919 -
Flags: review?(jonas) → review+
Updated•12 years ago
|
Keywords: checkin-needed
Comment 10•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/dc011fa9cc86
https://hg.mozilla.org/releases/mozilla-beta/rev/6031db9484d0
Keywords: checkin-needed
Comment 11•12 years ago
|
||
Setting priority based on triage discussions. Feel free to decrease priority if you disagree.
Priority: -- → P2
Assignee | ||
Comment 12•12 years ago
|
||
Assignee | ||
Comment 13•12 years ago
|
||
Whiteboard: leave-open
Comment 14•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
Comment 15•12 years ago
|
||
Updated•11 years ago
|
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in
before you can comment on or make changes to this bug.
Description
•