gecko-dev

Andrew McCreight 5dec0e0beb Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian This patch was autogenerated by my decomponents.py It covers almost every file with the extension js, jsm, html, py, xhtml, or xul. It removes blank lines after removed lines, when the removed lines are preceded by either blank lines or the start of a new block. The "start of a new block" is defined fairly hackily: either the line starts with //, ends with */, ends with {, <![CDATA[, """ or '''. The first two cover comments, the third one covers JS, the fourth covers JS embedded in XUL, and the final two cover JS embedded in Python. This also applies if the removed line was the first line of the file. It covers the pattern matching cases like "var {classes: Cc, interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove the entire thing if they are all either Ci, Cr, Cc or Cu, or it will remove the appropriate ones and leave the residue behind. If there's only one behind, then it will turn it into a normal, non-pattern matching variable definition. (For instance, "const { classes: Cc, Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes "const CC = Components.Constructor".) MozReview-Commit-ID: DeSHcClQ7cG --HG-- extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b	2018-02-06 09:36:57 -08:00
..
multi-e10s-update	Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian	2018-02-06 09:36:57 -08:00
README.md	…

Andrew McCreight 5dec0e0beb Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian

This patch was autogenerated by my decomponents.py

It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.

It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.

It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)

MozReview-Commit-ID: DeSHcClQ7cG

--HG--
extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b

2018-02-06 09:36:57 -08:00

multi-e10s-update

Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian

2018-02-06 09:36:57 -08:00

README.md

…

README.md

This directory contains tests that are flaky when run with other tests but that we don't want to disable and where it's not trivial to make the tests not flaky at this time, but we have a plan to fix them via systemic fixes that are improving the codebase rather than hacking a test until it works.

This directory and ugly hack structure needs to exist because of multi-e10s propagation races that will go away when we finish implementing the multi-e10s overhaul for ServiceWorkers. Most specifically, unregister() calls need to propagate across all content processes. There are fixes on bug 1318142, but they're ugly and complicate things.

Specific test notes and rationalizations:

multi-e10s-update: This test relies on there being no registrations existing at its start. The preceding test that induces the breakage (browser_force_refresh.js) was made to clean itself up, but the unregister() race issue is not easily/cleanly hacked around and this test will itself become moot when the multi-e10s changes land.