This wasn't really used anymore.
We are fetching the database from the server runtime in order to support
remote debugging correctly, where frontend CSS may be different from debuggee CSS.
Differential Revision: https://phabricator.services.mozilla.com/D187492
This wasn't really used anymore.
We are fetching the database from the server runtime in order to support
remote debugging correctly, where frontend CSS may be different from debuggee CSS.
Differential Revision: https://phabricator.services.mozilla.com/D187492
This patch pulls in the code from https://github.com/codehag/debugger-talos-example into the `app` folder.
The code structure is also now slightly different. There are now two folders, which `app` and `app-build`
The code in the `app` folder should now be where any further changes are made, this then gets built into `app_build` folder
which is used for the tests.
The idea is that the code in the `app-build` folder should not be changed manually, but it is rather always built
from `app`. See the readme for details.
Differential Revision: https://phabricator.services.mozilla.com/D184455
Paths mentioned between <code> tags are looked up in the repo, and an
error is emitted if they don't exist. This should make license.html more
resilient to code removal / move.
Idea inspired by a discussion with glandium.
This patch contains both the linter extension and the normalisation of
license.html to pass the linting.
Differential Revision: https://phabricator.services.mozilla.com/D180933
Currently dot files (e.g. .eslintrc.js) are not checked in the full run on CI.
Also ignores .gradle/ directory as that it a cache.
Differential Revision: https://phabricator.services.mozilla.com/D177261
Enables Prettier for (these don't need to be excluded):
- extensions/pref/autoconfig/test/unit/autoconfig.js
- services/sync/tests/unit/prefs_test_prefs_store.js
Removes duplications where the files are already ignored in the .eslintignore section.
Re-organises the structure of the remaining parts to make it clearer why they are being excluded.
Differential Revision: https://phabricator.services.mozilla.com/D176636
Unfortunately Prettier does not currently support multiple ignore files (see bug 1825508). Therefore we have to duplicate the entries from .eslintignore/Generated.txt/ThirdPartyPaths.txt for the time being.
Differential Revision: https://phabricator.services.mozilla.com/D174762
Unfortunately Prettier does not currently support multiple ignore files (see bug 1825508). Therefore we have to duplicate the entries from .eslintignore/Generated.txt/ThirdPartyPaths.txt for the time being.
Differential Revision: https://phabricator.services.mozilla.com/D174762
The shell module loader was rewritten to C++ in bug 1637529.
"jsrtfuzzing-example.js" was changed to appease prettier, now that it's enabled.
Differential Revision: https://phabricator.services.mozilla.com/D153151
There are some complications here to handle unpackaged and packaged
builds. In addition, there could be a difference between App prefs
and GRE prefs. Since the underlying backgroundtasks code is built as
part of Gecko (i.e., `toolkit/...` rather than `browser/...`) I have
favoured GRE prefs. I think, however, that what is written will work
for App-specific prefs, but I'm not concerned with that detail at this
time.
This also add tests for backgroundtask-specific prefs, which are
structured as both xpcshell and mochitest-chrome tests because
locally, the former tests unpackaged builds and the latter can
accommodate testing packaged builds. We could use mochitest-chrome
for both, but this has been pleasant to work with locally.
Differential Revision: https://phabricator.services.mozilla.com/D97510
There are some complications here to handle unpackaged and packaged
builds. In addition, there could be a difference between App prefs
and GRE prefs. Since the underlying backgroundtasks code is built as
part of Gecko (i.e., `toolkit/...` rather than `browser/...`) I have
favoured GRE prefs. I think, however, that what is written will work
for App-specific prefs, but I'm not concerned with that detail at this
time.
This also add tests for backgroundtask-specific prefs, which are
structured as both xpcshell and mochitest-chrome tests because
locally, the former tests unpackaged builds and the latter can
accommodate testing packaged builds. We could use mochitest-chrome
for both, but this has been pleasant to work with locally.
Differential Revision: https://phabricator.services.mozilla.com/D97510
There are some complications here to handle unpackaged and packaged
builds. In addition, there could be a difference between App prefs
and GRE prefs. Since the underlying backgroundtasks code is built as
part of Gecko (i.e., `toolkit/...` rather than `browser/...`) I have
favoured GRE prefs. I think, however, that what is written will work
for App-specific prefs, but I'm not concerned with that detail at this
time.
This also add tests for backgroundtask-specific prefs, which are
structured as both xpcshell and mochitest-chrome tests because
locally, the former tests unpackaged builds and the latter can
accommodate testing packaged builds. We could use mochitest-chrome
for both, but this has been pleasant to work with locally.
Differential Revision: https://phabricator.services.mozilla.com/D97510
It seems that the recommended Prettier extension for VSCode automatically formats CSS.
I guess this is also true for any editor extension that formats on save.
However ./mach lint is not checking CSS formatting issues, and we have not auto-formatted CSS files in the tree.
This can lead to unexpected formatting changes for developers using VSCode.
Differential Revision: https://phabricator.services.mozilla.com/D58593
--HG--
extra : moz-landing-system : lando
This makes prefs definition simpler, more consistent, and less error-prone.
Differential Revision: https://phabricator.services.mozilla.com/D41145
--HG--
extra : moz-landing-system : lando
This makes prefs definition simpler, more consistent, and less error-prone.
Differential Revision: https://phabricator.services.mozilla.com/D41324
--HG--
extra : moz-landing-system : lando
This makes prefs definition simpler, more consistent, and less error-prone.
The patch also changes the form of the "not Android" condition to one used more
widely in all.js.
Differential Revision: https://phabricator.services.mozilla.com/D41299
--HG--
extra : moz-landing-system : lando
