Closed
Bug 1312824
Opened 8 years ago
Closed 4 years ago
Consider repackaging devtools as an add-on
Categories
(Firefox for Android Graveyard :: General, defect, P3)
Firefox for Android Graveyard
General
Tracking
(firefox52 wontfix)
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
firefox52 | --- | wontfix |
People
(Reporter: snorp, Unassigned)
References
Details
The devtools appear to use about 1.3MB of space uncompressed. If we removed this from the omni.jar and instead put it in an addon we could reclaim maybe 800k.
Comment 1•8 years ago
|
||
Naive question - since as far as I know any devtool "usage" is effectively done remotely via the WebIDE anyway, to what extent are the devtools actually required on Fennec? Having said that, putting the whole shebang into an addon might still be easier than splitting this up into the bits that are required and Fennec and those that can be left out.
Comment 2•8 years ago
|
||
Mass wontfix for bugs affecting firefox 52.
[triage] Bulk edit from title: this is a non-critical issue or [meta] bug.
Priority: -- → P3
Comment 4•4 years ago
|
||
Thank you so much for the information keep suggesting us such informative post i will recommend this post to others
https://www.mygreatlakes.me/
Comment 5•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•