Wifi: Rename the DOM service to not have the ns prefix

RESOLVED FIXED

Status

()

Core
DOM: Device Interfaces
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: mrbkap, Assigned: mrbkap)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

5 years ago
See bug 732982, comment 15.
(Assignee)

Comment 1

5 years ago
Created attachment 606632 [details] [diff] [review]
For the DOM service
Attachment #606632 - Flags: review?(philipp)
(Assignee)

Comment 2

5 years ago
Created attachment 606633 [details] [diff] [review]
For the chrome side
Attachment #606633 - Flags: review?(philipp)
Attachment #606633 - Flags: review?(philipp) → review+
Comment on attachment 606633 [details] [diff] [review]
For the chrome side

So one thing that occurred to me as well: WifiWorker and its companions should probably live in dom/system/gonk. But we can do that in a separate bug, and perhaps even while or after we consolidate some of the code in the network manager.
Attachment #606632 - Flags: review?(philipp) → review+
Comment on attachment 606632 [details] [diff] [review]
For the DOM service

Also, as per dev-webapi discussions: the "manager" part of the DOM API is pretty useless. navigator.wifi is much nicer (because shorter) than navigator.wifiManager (modulo moz prefix). But that, too, can be a follow-up bug.
(Assignee)

Comment 5

5 years ago
Yeah, I filed that as bug 736088.
(Assignee)

Comment 6

5 years ago
https://hg.mozilla.org/mozilla-central/rev/350ed35543d2
https://hg.mozilla.org/mozilla-central/rev/c22568c8cf0e
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.