Closed Bug 1272494 Opened 8 years ago Closed 6 years ago

Use distinct chrome:// space for android, chrome://browser/ -> chrome://mobile/

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Pike, Unassigned)

Details

(Keywords: addon-compat)

chrome:// urls aren't all that universal, one aspect of it being that fennec uses chrome://browser/ and desktop does, too. And they use the same urls, for different things. This might have add-on compat impact, but margeret said on https://mail.mozilla.org/pipermail/mobile-firefox-dev/2016-May/002081.html that that would be OK. Jorge, do we have a way to query mxr on addons for mobile only? I have a local patch that I didn't actually test yet, I pushed that as part of https://treeherder.mozilla.org/#/jobs?repo=try&revision=0e82723c0237 to let try figure this out.
> Jorge, do we have a way to query mxr on addons for mobile only? No, but there aren't that many Android add-ons, so they could be checked semi-manually.
The prior patch failed on missing chrome registry changes, which https://treeherder.mozilla.org/#/jobs?repo=try&revision=44aa1fa4e8eb has fixed. There's a reliable failure on chrome mochitest, https://treeherder.mozilla.org/#/jobs?repo=try&revision=44aa1fa4e8eb&selectedJob=20839905, not sure how to fix that, as I don't really understand what might be broken.

Cleaning up local patches, I don't think this is worth it anymore.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.