For simple rules like function spacing, we can auto-fix these across the code
base so they are followed in a consistent way.
To generate this patch, I ran:
./mach eslint devtools --no-ignore --fix
After this, I reverted any changes to third party files that we really do want
to ignore.
MozReview-Commit-ID: 6Q8BApkAW20
This patch was generated by the command:
find * -type f -exec sed -i -f ../mozpropsub {} \;
in the root of the repository, with the file ../mozpropsub containing:
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
s/\<MozPaddingEnd\>/paddingInlineEnd/g
s/\<MozPaddingStart\>/paddingInlineStart/g
s/\<MozMarginEnd\>/marginInlineEnd/g
s/\<MozMarginStart\>/marginInlineStart/g
s/\<MozBorderEnd\>/borderInlineEnd/g
s/\<MozBorderEndColor\>/borderInlineEndColor/g
s/\<MozBorderEndStyle\>/borderInlineEndStyle/g
s/\<MozBorderEndWidth\>/borderInlineEndWidth/g
s/\<MozBorderStart\>/borderInlineStart/g
s/\<MozBorderStartColor\>/borderInlineStartColor/g
s/\<MozBorderStartStyle\>/borderInlineStartStyle/g
s/\<MozBorderStartWidth\>/borderInlineStartWidth/g
The diffs for the following files:
layout/style/nsCSSPropAliasList.h
layout/style/test/property_database.js
layout/style/test/test_value_computation.html
were then manually removed from the patch.
MozReview-Commit-ID: 8fbYnlZcn9U
By default it switches to a contentEditable when a custom UA is applied, which
causes errors when trying to insert a controller.
MozReview-Commit-ID: AdRUpO3NHNF
Changes the way that source files are loaded in the editor. Previously,
source text and mode were set on the existing editor document.
Now, source files are their own CodeMirror Documents, so when it comes time
to showing them in the editor, it's just a matter of swapping one
document for another.
Notes:
+ The DebuggerView now has a _setEditorDocument method for showing a
source document
+ The Editor now has support for creating documents and replacing
documents.
MozReview-Commit-ID: HrkiHrsJPOB
This patch updates the Source Editor contextmenu's UX. Prior to the
patch, the menu would show the option "Add conditional breakpoint" even
when there was a conditional breakpoint. Now, that option reads "Edit
conditional breakpoint".
This patch updates the Source Editor contextmenu's UX. Prior to the
patch, the menu would show the option "Add conditional breakpoint" even
when there was a conditional breakpoint. Now, that option reads "Edit
conditional breakpoint".
* * *
Bug 1132557 - Part 3: Apply CodeMirror customization for search.js r=bgrins
* * *
Bug 1132557 - Part 8: Editor config option should be updated r=bgrins
* * *
Bug 1132557 - Part 9: Editor should emit a cursorActivity on setCursor r=bgrins
* * *
Bug 1132557 - Part 10: Make Debugger breadrumbs keyboard access test by refocusing the stack frame r=bgrins
* * *
Bug 1132557 - Part 11: Scratchpad should use capture on the paste event r=bgrins
* * *
Bug 1132557 - Part 12: Stylesheet Editor should always batch up updates r=bgrins
Break DevTools theme files out of browser.jar and move to a new DevTools
specific jar. Update all paths of the form:
chrome://browser/skin/devtools/<X>
to
chrome://devtools/skin/<Y>
where <Y> is the source tree path that comes after /devtools/client.
In a following patch, all DevTools moz.build files will use DevToolsModules to
install JS modules at a path that corresponds directly to their source tree
location. Here we rewrite all require and import calls to match the new
location that these files are installed to.
Break DevTools content files out of browser.jar and move to a new DevTools
specific jar. Update all paths of the form:
chrome://browser/content/devtools/<X>
to
chrome://devtools/content/<Y>
where <Y> is the source tree path that comes after /devtools/client.
Move major DevTools files to new directories using the following steps:
hg mv browser/devtools devtools/client
hg mv toolkit/devtools/server devtools/server
hg mv toolkit/devtools devtools/shared
No other changes are made.
