Commit e2b52a13 authored by Sylvestre Ledru's avatar Sylvestre Ledru
Browse files

Bug 1807899 - Remove the trailing whitespace and Windows CR on md files... 

Bug 1807899 - Remove the trailing whitespace and Windows CR on md files r=linter-reviewers,necko-reviewers,marco,jesup

Differential Revision: https://phabricator.services.mozilla.com/D165662
parent e3f27e55

devtools/docs/contributor/contributing/code-reviews-checklist.md

+0 −1
Original line number Diff line number Diff line
@@ -56,4 +56,3 @@ It can also be useful for patch authors: if the changes comply with these guidel 
* R+: the code should land as soon as possible.

* R+ with comments: there are some comments, but they are minor enough, or don't require a new review once addressed, trust the author.

* R cancel / R- / F+: there is something wrong with the code, and a new review is required.

devtools/docs/contributor/contributing/coding-standards.md

+0 −1
Original line number Diff line number Diff line
@@ -7,4 +7,3 @@ We have pages defining standards, best practices and tips for various languages 
* [JavaScript](./javascript.md)

* [CSS](./css.md)

* [SVG](../frontend/svgs.md)

devtools/docs/contributor/contributing/css.md

+1 −2
Original line number Diff line number Diff line
@@ -128,4 +128,3 @@ The Mozilla way is to perform the toggle using an attribute rather than a class: 


* Use `:empty` to match a node that doesn't have children.

* Usually, if `margin` or `padding` has 4 values, something is wrong. If the left and right values are asymmetrical, you're supposed to use `-start` and `-end`. If the values are symmetrical, use only 3 values (see localization section).

devtools/docs/contributor/contributing/eslint.md

+0 −1
Original line number Diff line number Diff line
@@ -155,4 +155,3 @@ This should help you write eslint-clean code: 
* ESLint also runs on `<script>` tags in HTML files, so if you create new HTML test files for mochitests for example, make sure that JavaScript code in those files is free of ESLint errors.

* Depending on how a dependency is loaded into a file, the symbols this dependency exports might not be considered as defined by ESLint. For instance, using `Cu.import("some.jsm")` doesn't explicitly say which symbols are now available in the scope of the file, and so using those symbols will be consider by ESLint as using undefined variables. When this happens, please avoid using the `/* globals ... */` ESLint comment (which tells it that these variables are defined). Instead, please use `/* import-globals-from relative/path/to/file.js */`. This way, you won't have a list of variables to maintain manually, the globals are going to be imported dynamically instead.

* In test files (xpcshell and mochitest), all globals from the corresponding `head.js` file are imported automatically, so you don't need to define them using a `/* globals ... */` comment or a `/* import-globals-from head.js */` comment.

devtools/docs/contributor/files/README.md

+0 −1
Original line number Diff line number Diff line
@@ -10,4 +10,3 @@ This page provides a very top level overview of what is on each directory in the 
* `devtools/client`: Code for the front-end side of our tools. In theory, each directory corresponds to a panel, but this is not always the case. This directory is only shipped with desktop Firefox, as opposed to other directories above, which are shipped with all Gecko products (Firefox for Android, etc.)

  * `devtools/client/locales`: Strings used in the client front-end.

  * `devtools/client/themes`: CSS and images used in the client front-end.