Closed
Bug 959845
Opened 11 years ago
Closed 5 years ago
Disable the network API on desktop
Categories
(Core :: DOM: Core & HTML, task, P5)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1020758
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
I'm not sure why dom.network.enabled is true everywhere, it seems like that was done in bug 677166 without much discussion. Jonas, do you agree that we should restrict this to b2g for now?
Flags: needinfo?(jonas)
Comment 1•11 years ago
|
||
I don't see much reason to not enable it everywhere. In the interest of cross-device compat, it should remain enabled everywhere, even if it does not make that much sense on most desktop systems (but maybe on notebooks with 3G modems if this is recognized).
Reporter | ||
Comment 2•11 years ago
|
||
Well, we're looking into alternate APIs right now, so we're clearly not ready to expose anything here to the broader web I think.
Comment 3•11 years ago
|
||
Are there overlapping parts for the implemented vs the alternate APIs? In this case, I'd expose the overlapping parts (because they seem to have consensus) and remove all other parts.
Reporter | ||
Comment 4•11 years ago
|
||
(In reply to comment #3)
> Are there overlapping parts for the implemented vs the alternate APIs? In this
> case, I'd expose the overlapping parts (because they seem to have consensus)
> and remove all other parts.
The new proposal is under navigator.netInfo. But the reason why I filed this bug was that our desktop implementation just returns bogus values. We have a real implementation on Android but it's not clear to me if we want to keep that around as well, and it would be nice if we could eventually avoid exposing both versions of this API.
Reporter | ||
Updated•11 years ago
|
Summary: Disable the network API on desktop and mobile → Disable the network API on desktop
We should definitely remove this API from platforms where at least .bandwidth is implemented. The implementations that just return hardcoded values don't seem to add any value.
I thought that we only had an implementation on Android right now. I.e. that even B2G wasn't implemented? Bug 796539 is still marked as unfixed, which indicates that's the case.
If so, I think we should disabled this API everywhere except for Android.
Flags: needinfo?(jonas)
Updated•11 years ago
|
Comment 6•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Comment 7•6 years ago
|
||
ehsan, do you recall which network API this bug is/was about. Some b2g thingie or https://searchfox.org/mozilla-central/source/dom/webidl/NetworkInformation.webidl
I think some b2g.
Flags: needinfo?(ehsan)
Reporter | ||
Comment 8•6 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/ae8a5c6d6340 suggests that this pref used to control the navigator.mozConnection API.
Flags: needinfo?(ehsan)
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Comment 9•5 years ago
|
||
This has already been done with Firefox 31.
Status: NEW → RESOLVED
Type: defect → task
Closed: 5 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•