Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
I wasn't sure what we should show in the case of unofficial builds. Curently the logo is just hidden for those builds.
Differential Revision: https://phabricator.services.mozilla.com/D31286
--HG--
extra : moz-landing-system : lando
On startup of a fresh dedicated profile show a welcome page and a modal dialog
to explain what has happened.
--HG--
extra : rebase_source : 1505cf27f900070debc1f9e1c71ec4bef3bc099d
extra : source : 05200c5388b4f7adc4414268727458515d7b9ed9
On startup of a fresh dedicated profile show a welcome page and a modal dialog
to explain what has happened.
--HG--
extra : rebase_source : a033baf831aa8b9fcfa95d1f921364632a837390
default48.png and icon48.png is same file. So we should remove one side.
MozReview-Commit-ID: 6WuxH0QFQ25
--HG--
extra : rebase_source : 1f6545daf3968fa06079358c7a3edce6a484a582
Now, default48.png is highest resolition icon for Firfox/GTK. So we should add
default64.png (from icon64.png) and default128.png (from mozicon128.png) for
HiDPI. Also mozicon128.png is for Linux distribution, we should move to
correct place for our GTK icons.
MozReview-Commit-ID: BeLXzUcOgQu
--HG--
rename : browser/branding/aurora/mozicon128.png => browser/branding/aurora/default128.png
rename : browser/branding/aurora/content/icon64.png => browser/branding/aurora/default64.png
rename : browser/branding/nightly/mozicon128.png => browser/branding/nightly/default128.png
rename : browser/branding/nightly/content/icon64.png => browser/branding/nightly/default64.png
rename : browser/branding/official/mozicon128.png => browser/branding/official/default128.png
rename : browser/branding/official/content/icon64.png => browser/branding/official/default64.png
rename : browser/branding/unofficial/mozicon128.png => browser/branding/unofficial/default128.png
rename : browser/branding/unofficial/content/icon64.png => browser/branding/unofficial/default64.png
extra : rebase_source : 8cba5f3ae1420452d6f6a11f8df38bc04702bf17
default48.png and icon48.png is same file. So we should remove one side.
MozReview-Commit-ID: 6WuxH0QFQ25
--HG--
extra : rebase_source : 70f45a058fe61dfd7b5331130607d231428fbff7
Now, default48.png is highest resolition icon for Firfox/GTK. So we should add
default64.png (from icon64.png) and default128.png (from mozicon128.png) for
HiDPI. Also mozicon128.png is for Linux distribution, we should move to
correct place for our GTK icons.
MozReview-Commit-ID: BeLXzUcOgQu
--HG--
rename : browser/branding/aurora/mozicon128.png => browser/branding/aurora/default128.png
rename : browser/branding/aurora/content/icon64.png => browser/branding/aurora/default64.png
rename : browser/branding/nightly/mozicon128.png => browser/branding/nightly/default128.png
rename : browser/branding/nightly/content/icon64.png => browser/branding/nightly/default64.png
rename : browser/branding/official/mozicon128.png => browser/branding/official/default128.png
rename : browser/branding/official/content/icon64.png => browser/branding/official/default64.png
rename : browser/branding/unofficial/mozicon128.png => browser/branding/unofficial/default128.png
rename : browser/branding/unofficial/content/icon64.png => browser/branding/unofficial/default64.png
extra : rebase_source : 2048530d25965f20ffd9aa6b895f7795e7efeda2
This removes the unnecessary setting of c-basic-offset from all
python-mode files.
This was automatically generated using
perl -pi -e 's/; *c-basic-offset: *[0-9]+//'
... on the affected files.
The bulk of these files are moz.build files but there a few others as
well.
MozReview-Commit-ID: 2pPf3DEiZqx
--HG--
extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204
This patch was generated by the command:
find . -name "*.css" -exec sed -i -f mozpropsub {} \;
in the root of a mozilla-central tree, with the file mozpropsub
containing the contents:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g
While I didn't manually review all the changes, I did review the list of
files, and manually reviewed the changes in the files that I thought
were more interesting.
Note that there are a few tests that should be fixed up as well, but
I'll do that in a later patch.
MozReview-Commit-ID: EiQTuuV0MNQ
Every directory with a jar.mn now has JAR_MANIFESTS defined in its
moz.build file.
We also removed the may_skip special consideration of jar.mn files
because this information is now available during tier traversal by the
reader courtesy of the variables being present in moz.build files.
--HG--
extra : rebase_source : 21049b15e6bd9cf65b0805ccaccc4ba5aae93c98
extra : amend_source : 0b1ea866d725beef92d37c6f6d475369ac002e19