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)

x86
Gonk (Firefox OS)
defect

Tracking

()

RESOLVED FIXED
mozilla20
blocking-basecamp +
Tracking Status
firefox18 --- fixed
firefox19 --- fixed
firefox20 --- fixed

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.
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".
(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.
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.
Attached patch patchSplinter Review
Lets change it. I checked the Gaia permissions and they all support mozBluetooth and bluetooth so we are good there.
Assignee: nobody → anygregor
blocking-basecamp: --- → ?
Attachment #685760 - Flags: review?(kyle)
Attachment #685760 - Flags: review?(kyle) → review+
blocking-basecamp: ? → +
This should land once we removed all the mozBluetooth permissions in Gaia.
Attachment #685773 - Flags: review?(kyle)
Attachment #685773 - Flags: review?(kyle) → review+
Whiteboard: leave-open
Attached file PR pointer
Attachment #685919 - Flags: review?(jonas)
PR 6670 should only land after https://bug815572.bugzilla.mozilla.org/attachment.cgi?id=685760 is distributed to all trees.
Setting priority based on triage discussions.  Feel free to decrease priority if you disagree.
Priority: -- → P2
https://hg.mozilla.org/mozilla-central/rev/6e8ee650b33c
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
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.

Attachment

General

Created:
Updated:
Size: