Closed
Bug 1235596
Opened 8 years ago
Closed 3 years ago
Investigate shipping a blocklist.xml on Android
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mfinkle, Unassigned)
Details
We attempt to package the XML file, but it only exists in /browser
Comment 1•8 years ago
|
||
Kev, how is the add-on blocklist maintained for desktop? Should we include the same (or a similar) blocklist for Android?
Flags: needinfo?(kev)
Comment 2•8 years ago
|
||
Jorge maintains the file, and it may make sense to add a modification for Android-compatible addons only, given file sizes (although it's not huge). Just for clarity, this is only related to the packaged blocklist file we provide on install, correct?
Flags: needinfo?(kev) → needinfo?(jorge)
Comment 3•8 years ago
|
||
The blocklist is currently maintained via an admin form on AMO, and the same XML file is sent to all clients that use it. The latest copy of the blocklist XML is added when Firefox is built. The blocklist system is being moved to a Kinto system and will be served as JSON. I think the expectation is to finish the move by Q3.
Flags: needinfo?(jorge)
Comment 4•3 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: 3 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•3 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
•