93eea604a7de62aa38fe44445f57fcf4b4225f71: Bug 1473263 - Show "No fonts" message when there are no fonts used on the selected element or its descendants. r=pbro draft
Razvan Caliman <rcaliman@mozilla.com> - Wed, 04 Jul 2018 18:39:06 +0200 - rev 814137
Push 115122 by bmo:rcaliman@mozilla.com at Wed, 04 Jul 2018 17:13:31 +0000
Bug 1473263 - Show "No fonts" message when there are no fonts used on the selected element or its descendants. r=pbro MozReview-Commit-ID: Bkgs6ulw8nD
6b5ab01eee8430daa2ab1102d9d77bff2bb10070: Bug 1452706 - Remove the now redundant ESLint rule require-expected-throws-or-rejects. r?mikedeboer draft
Mark Banner <standard8@mozilla.com> - Tue, 03 Jul 2018 20:22:01 +0100 - rev 814136
Push 115121 by bmo:standard8@mozilla.com at Wed, 04 Jul 2018 17:00:36 +0000
Bug 1452706 - Remove the now redundant ESLint rule require-expected-throws-or-rejects. r?mikedeboer MozReview-Commit-ID: 7CXrVV6x5I6
c266e610f29dc7bbe9cc9865dfb2cf263bba128a: Bug 1452706 - Make the 'expected' argument to Assert.throws/rejects required rather than optional. r?mikedeboer draft
Mark Banner <standard8@mozilla.com> - Fri, 01 Jun 2018 14:33:31 +0100 - rev 814135
Push 115121 by bmo:standard8@mozilla.com at Wed, 04 Jul 2018 17:00:36 +0000
Bug 1452706 - Make the 'expected' argument to Assert.throws/rejects required rather than optional. r?mikedeboer MozReview-Commit-ID: 25flGw5sWga
7e67b6aaa381016ba52d1f906dfbd6d4c6babba0: Bug 1452706 - Add the 'expected' arguments to throws/rejects for devtools/shared/sourcemap. r?yulia draft
Mark Banner <standard8@mozilla.com> - Tue, 03 Jul 2018 20:16:20 +0100 - rev 814134
Push 115121 by bmo:standard8@mozilla.com at Wed, 04 Jul 2018 17:00:36 +0000
Bug 1452706 - Add the 'expected' arguments to throws/rejects for devtools/shared/sourcemap. r?yulia MozReview-Commit-ID: AdOD0Txwdi7
05bbde32436d785c2adc57aab9a33e3305d4d791: Bug 1467736: Add support for DllBlocklist_Shutdown;r?aklotz draft
Carl Corcoran <ccorcoran@mozilla.com> - Wed, 20 Jun 2018 09:21:56 +0200 - rev 814133
Push 115120 by bmo:ccorcoran@mozilla.com at Wed, 04 Jul 2018 16:50:11 +0000
Bug 1467736: Add support for DllBlocklist_Shutdown;r?aklotz MozReview-Commit-ID: Gu7SodOTVqd
a40f8505d31dd1381b8b82b36c1b0a9194e587a4: Bug 550528 - Correct click grouping on Windows (like for quadruple-clicks) draft
h-h <henrik.hank@aol.de> - Wed, 04 Jul 2018 18:24:09 +0200 - rev 814132
Push 115119 by bmo:henrik.hank@aol.de at Wed, 04 Jul 2018 16:32:23 +0000
Bug 550528 - Correct click grouping on Windows (like for quadruple-clicks) Grouping of clicks, based on temporal and spatial boundaries, means the recognition of double-, triple-, quadruple-, quintuple-clicks etc. Use the "testcase" attachment of the bug which is an HTML file with JavaScript. On Mac, Firefox (allegedly) already allows infinite grouping of clicks. Also, Opera and Chrome allow for infinite grouping of clicks, at least on Windows. Until now, on Windows, only double- and triple-clicks are recognized, which affects selection behavior and renders the config option `about:config?filter=browser.triple_click_selects_paragraph` useless. When `false`, quadruple-clicks should select the paragraph. (Use, e.g., Wikipedia articles for testing.) Furthermore, it prevents us from defining behavior for quintuple-, sextuple-clicks etc. Not only does `nsWindow.cpp` restrict the maximum amount of grouped clicks, but it also contains quite a number of out-of-date and wrong comments in the respective section. Hence, I also restructed the method that does the click grouping for more clarity. I created sections because it is a very long method. (Changing the order of code blocks was necessary anyway, because `TouchEventShouldStartDrag()` expects `eMouseDoubleClick`, if applicable, which, with this patch, Windows does not send anymore, but we have our own recognition that changes `eMouseDown` to `eMouseDoubleClick`.) At first, please take a general look at the changes and answer my questions in the `FIXME` texts. Then, I think, it would be best that I rebase the changes by means of a temporary Git repository to create a series of commits that you can review easier to verify that I didn't make mistakes in this important piece of code. MozReview-Commit-ID: 8wtxtHb8ZwE
0b53d5877431f25bbcdac9172d7bd94557fb8fb2: Bug 1473275 - Remove the details expander in the Clear Recent History dialog. r=johannh draft
Paolo Amadini <paolo.mozmail@amadzone.org> - Wed, 04 Jul 2018 17:27:15 +0100 - rev 814131
Push 115118 by paolo.mozmail@amadzone.org at Wed, 04 Jul 2018 16:28:44 +0000
Bug 1473275 - Remove the details expander in the Clear Recent History dialog. r=johannh MozReview-Commit-ID: 99XDExBbRkp
3001d717d8d7f0cea9b05a6c6ab45a442c5c5c67: Bug 1467824 - Port raptor-speedometer google chrome to linux64 and win7/10 (wip) draft
Rob Wood <rwood@mozilla.com> - Wed, 27 Jun 2018 15:44:25 -0400 - rev 814130
Push 115117 by rwood@mozilla.com at Wed, 04 Jul 2018 15:55:46 +0000
Bug 1467824 - Port raptor-speedometer google chrome to linux64 and win7/10 (wip) MozReview-Commit-ID: FXXsRNFZTPt
d3b806f8bdd19d011f3c8680fd3a6f00e8882772: Bug 1121705 - Look at window handles decrement when closing tab. r?whimboo draft
Andreas Tolfsen <ato@sny.no> - Wed, 04 Jul 2018 16:36:05 +0100 - rev 814129
Push 115116 by bmo:ato@sny.no at Wed, 04 Jul 2018 15:40:56 +0000
Bug 1121705 - Look at window handles decrement when closing tab. r?whimboo When Puppeteer opens a new tab using various strategies it relies on the list of window handles increasing. When performing the reverse operation of closing a tab, it looks at the length of <tab> chrome elements in the UI. This changes the close operation to use the same mechanism as opening a new tab to determine if the tab has been closed. This seems to be as reliable as looking at the number of <tab> elements. As part of a forthcoming window tracking refactoring of Marionette (https://bugzilla.mozilla.org/show_bug.cgi?id=marionette-window-tracking), the list of window handles will be made even more reliable: a content browser will not appear in the window handle list until both the tab and it's linked content browser has been created and properly initialised. MozReview-Commit-ID: FY5vGBpn64R
dc50f0665660956785851df6ed998f6ca209a262: Bug 1472676: Add curly brackets. draft
Robert Bartlensky <rbartlensky@mozilla.com> - Wed, 04 Jul 2018 16:37:02 +0100 - rev 814128
Push 115115 by bmo:rbartlensky@mozilla.com at Wed, 04 Jul 2018 15:39:17 +0000
Bug 1472676: Add curly brackets. MozReview-Commit-ID: 7sgBIGX4RFj
f511ccfd9e2f85adb8b5f389fd2424ba2daf3e25: Bug 1463376 - Update to latest Google Play Services version r?nalexander draft
Andrei Lazar <andrei.a.lazar@softvision.ro> - Wed, 04 Jul 2018 18:34:02 +0300 - rev 814127
Push 115114 by bmo:andrei.a.lazar@softvision.ro at Wed, 04 Jul 2018 15:35:29 +0000
Bug 1463376 - Update to latest Google Play Services version r?nalexander Updated google play services version as part of work of the Oreo migration and removed unused libraries from gradle. MozReview-Commit-ID: BKCWs938k3q ***
aefb87ba89cdd65c2c4f0461d9078b34dd5f74bb: Bug 1472966 - Miscellaneous tweaks to paddings, margins and borders for font editor. r=gl draft
Razvan Caliman <rcaliman@mozilla.com> - Wed, 04 Jul 2018 14:05:23 +0200 - rev 814126
Push 115113 by bmo:rcaliman@mozilla.com at Wed, 04 Jul 2018 15:31:03 +0000
Bug 1472966 - Miscellaneous tweaks to paddings, margins and borders for font editor. r=gl MozReview-Commit-ID: 5eCbnTdKvqO
af8d6a8cc01dec782bd4ffbcb2f9d3cc203b4640: Bug 1472966 - Miscellaneous tweaks to paddings, margins and borders for font editor. r=gl draft
Razvan Caliman <rcaliman@mozilla.com> - Wed, 04 Jul 2018 14:05:23 +0200 - rev 814125
Push 115112 by bmo:rcaliman@mozilla.com at Wed, 04 Jul 2018 15:26:33 +0000
Bug 1472966 - Miscellaneous tweaks to paddings, margins and borders for font editor. r=gl MozReview-Commit-ID: 5eCbnTdKvqO
66dcdc91a9607dc38ccdb5d4b1a8c3b5a01fb707: Bug 1471517 - Converts ChromeUtils.requestPerformanceMetrics as Promise - r?baku draft
Tarek Ziadé <tarek@mozilla.com> - Wed, 04 Jul 2018 17:05:19 +0200 - rev 814124
Push 115111 by tziade@mozilla.com at Wed, 04 Jul 2018 15:21:56 +0000
Bug 1471517 - Converts ChromeUtils.requestPerformanceMetrics as Promise - r?baku This ChromeUtils API now returns a promise that gets resolved once all the data has been collected via IPDL and the main process. The existing notification design and its related XPCOM classes are removed. MozReview-Commit-ID: CYKukBOC8yh
d5e1d0b4cbe110c3fc1f853cdeac888b50972c5e: Bug 1434751 - Add Restore Defaults button to Home draft
Andrei Oprea <andrei.br92@gmail.com> - Tue, 03 Jul 2018 20:02:26 +0200 - rev 814123
Push 115110 by bmo:andrei.br92@gmail.com at Wed, 04 Jul 2018 14:55:56 +0000
Bug 1434751 - Add Restore Defaults button to Home MozReview-Commit-ID: 5NRxEhPIImg
4f740526545327370ff84c29a5d9e17ccf02f0d2: Bug 1471660 - Integrate code coverage for A(test) junit test suite via JaCoCo plugin. r=nalexander,marco draft
Tudor-Gabriel Vîjială <tvijiala@mozilla.com> - Mon, 02 Jul 2018 11:32:35 +0100 - rev 814122
Push 115109 by bmo:tvijiala@mozilla.com at Wed, 04 Jul 2018 14:35:00 +0000
Bug 1471660 - Integrate code coverage for A(test) junit test suite via JaCoCo plugin. r=nalexander,marco MozReview-Commit-ID: ElYGmF6zoYg
608f9b1d2f70badbcebfbc549a5381a5715e1faf: Bug 1467824 - Port raptor-speedometer google chrome to linux64 and win10 (wip) draft
Rob Wood <rwood@mozilla.com> - Wed, 27 Jun 2018 15:44:25 -0400 - rev 814121
Push 115108 by rwood@mozilla.com at Wed, 04 Jul 2018 14:30:55 +0000
Bug 1467824 - Port raptor-speedometer google chrome to linux64 and win10 (wip) MozReview-Commit-ID: Lb5EiKzjAtp
113b2d4f3359010355367ed96908b960396ef391: Bug 1471843: Remove audioWorklet attribute from Window. r?karlt,baku draft
Arnaud Bienner <arnaud.bienner@gmail.com> - Tue, 03 Jul 2018 16:58:16 +0200 - rev 814120
Push 115107 by bmo:arnaud.bienner@gmail.com at Wed, 04 Jul 2018 14:26:06 +0000
Bug 1471843: Remove audioWorklet attribute from Window. r?karlt,baku MozReview-Commit-ID: 9SJRZ2keJpb
c7a48d01c9f67a0eb56ed5aa2adf70c79510851a: Bug 218415 - Add window.event. r?smaug. draft
Henri Sivonen <hsivonen@hsivonen.fi> - Wed, 04 Apr 2018 15:57:17 +0300 - rev 814119
Push 115106 by bmo:hsivonen@hsivonen.fi at Wed, 04 Jul 2018 14:25:33 +0000
Bug 218415 - Add window.event. r?smaug. window.event is set on the wrong window when the target and the callback are from different realms and the callback is an XPCOM callback. MozReview-Commit-ID: HXeUIicdMuT
f83e2c25fea1423d84c0b00f5b9045c90666fe50: Bug 1473309 - Move TabContextMenu and stray usercontext-related functions from browser.js to tabbrowser.js. r?bgrins draft
Dão Gottwald <dao@mozilla.com> - Wed, 04 Jul 2018 16:24:37 +0200 - rev 814118
Push 115105 by dgottwald@mozilla.com at Wed, 04 Jul 2018 14:25:14 +0000
Bug 1473309 - Move TabContextMenu and stray usercontext-related functions from browser.js to tabbrowser.js. r?bgrins MozReview-Commit-ID: CA3F65x08Kg
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip