Hi,
if we'd move all the fennec-specific chrome:// urls from
chrome://browser/ to chrome://mobile/, would that have a massive impact?
I guess the biggest question is about the impact on add-ons?
This is really only about chrome:// urls. This doesn't have impact on
where files are in mozilla-central, nor where they're in the omni.ja.
But anything external that'd rely on finding
chrome://browser/skin/images/scrubber.svg or locales, content, would break.
Background:
We have tons of problems with chrome overrides in the tree, both in
desktop and mobile. The problem is amplified by fennec sharing a URL
space with desktop, pretending to do the same thing, but totally not
doing anything remotely similar.
The chrome overrides are a big hurdle in finding out if our l10n setup
is sane. I filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1255382 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1255404
on some of the more scary ways in which we're broken right now.
These problems are part of our problem space that we don't have tests
that ensure that the strings we have in our repos actually correspond to
our code. Which is what I'm working on. Which I think is a key blocker
to get to the "one repo per locale for all channels" plan.
Axel
_______________________________________________
mobile-firefox-dev mailing list
mobile-firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/mobile-firefox-dev
