16b8136f47f172303132f7b86aa164f987a41ef7: Bug 1478564 - part 0: Add automated tests for TextEditRules::HandleNewLines() r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 26 Jul 2018 22:27:47 +0900 - rev 428681
Push 66970 by masayuki@d-toybox.com at Fri, 27 Jul 2018 08:39:48 +0000
Bug 1478564 - part 0: Add automated tests for TextEditRules::HandleNewLines() r=m_kato MozReview-Commit-ID: L55zBuflDBP
d7039031e380efda6b3fef5f9e55e41baa424c05: Bug 1307464 - Use HTMLTooltip in shader editor;r=nchevobbe
Julian Descottes <jdescottes@mozilla.com> - Thu, 26 Jul 2018 17:43:15 +0200 - rev 428680
Push 66969 by jdescottes@mozilla.com at Fri, 27 Jul 2018 07:39:28 +0000
Bug 1307464 - Use HTMLTooltip in shader editor;r=nchevobbe Migrate the ShaderEditor to use the HTMLTooltip instead of the old XUL-only Tooltip. The HTMLTooltip doesn't provide a builtin setTextContent API, so the shadereditor is now creating the markup for the tooltip and setting it as the content. The styles have been ported to shadereditor.css and now rely on theme variables. This will allow us to move all the old tooltip code to the old debugger folder, which will be the last consumer of the widget. MozReview-Commit-ID: HVyxtf0xM4x
910af1264f68e4d65e8e55d1605ba2e88196bb10: Bug 1439995 - [wdspec] Refactor user_prompt tests for Execute Script / Execute Async Script. r=ato
Henrik Skupin <mail@hskupin.info> - Thu, 26 Jul 2018 22:53:34 +0200 - rev 428679
Push 66968 by hskupin@mozilla.com at Fri, 27 Jul 2018 07:33:33 +0000
Bug 1439995 - [wdspec] Refactor user_prompt tests for Execute Script / Execute Async Script. r=ato To align with all the other commands the user_prompts.py test file has to contain tests for handling an open user prompt when calling the command. In case of both Execute Script and Execute Async Script the file contained tests where a user prompt got opened during the script execution. Tests for the latter situation are moved to a different test file. MozReview-Commit-ID: JeAROkAH9vk
5fcc35eafe56492b9fe0687a988330c3cce2da6c: Bug 1439995 - [marionette] Add user prompt checks for script execution commands. r=ato
Henrik Skupin <mail@hskupin.info> - Thu, 26 Jul 2018 22:04:56 +0200 - rev 428678
Push 66968 by hskupin@mozilla.com at Fri, 27 Jul 2018 07:33:33 +0000
Bug 1439995 - [marionette] Add user prompt checks for script execution commands. r=ato WebDriver:{ExecuteScript,ExecuteAsyncScript} were missing user prompt checks. MozReview-Commit-ID: KL8gTBfSTrU
156f576151ebdd20ce8dd251d4b25d5433fa8120: Bug 1407123 - Wait for the update task to be finished before running next test case. r=francois
Dimi Lee <dlee@mozilla.com> - Thu, 26 Jul 2018 18:26:19 +0000 - rev 428677
Push 66967 by dlee@mozilla.com at Fri, 27 Jul 2018 07:12:50 +0000
Bug 1407123 - Wait for the update task to be finished before running next test case. r=francois The test_partialUpdateV4() test case doesn't wait for the update task to be finished. It checks the status in the HTTP server side and then calls run_next_test(). However, when XPCShell test is done, it will trigger the shutdown process and hence interrupt the ongoing update task. This cause the xpcshell test receives an error since the update is interrupted and returns an error like NS_ERROR_UC_UPDATE_SHUTDOWNING. This patch also fixes a javascript error that we didn't stop the httpd server when cleanup. Differential Revision: https://phabricator.services.mozilla.com/D2360
dea04396335368380971c7ff6b39fae2c5439a44: Bug 1472238: compare old and new versions and prefer what we had r=lina
Ethan Glasser-Camp <ethan@betacantrips.com> - Fri, 29 Jun 2018 12:49:55 -0400 - rev 428676
Push 66966 by kcambridge@mozilla.com at Fri, 27 Jul 2018 07:10:10 +0000
Bug 1472238: compare old and new versions and prefer what we had r=lina When a component registers after having already registered once, there are two sources of truth for the version ID: one implicit in the connection to Megaphone, and one coming from the component call to addListener. Try to handle this more thoroughly. MozReview-Commit-ID: EsYgO0mzQ9w
fcc52b742b2feb197940024c2c1622c4cd4ab13f: Bug 1472238: ensure version is not an empty string r=lina
Ethan Glasser-Camp <ethan@betacantrips.com> - Fri, 29 Jun 2018 12:43:42 -0400 - rev 428675
Push 66966 by kcambridge@mozilla.com at Fri, 27 Jul 2018 07:10:10 +0000
Bug 1472238: ensure version is not an empty string r=lina MozReview-Commit-ID: CbPFJkl3vGr
bcb897d35e71db66f78a5f18fbda1963cff48684: Bug 1472238: hook up alwaysConnect pref changes r=lina
Ethan Glasser-Camp <ethan@betacantrips.com> - Fri, 29 Jun 2018 12:33:20 -0400 - rev 428674
Push 66966 by kcambridge@mozilla.com at Fri, 27 Jul 2018 07:10:10 +0000
Bug 1472238: hook up alwaysConnect pref changes r=lina The original code had a bug in that going from disabled to enabled would always connect, whereas actually we want to only connect if there are records (or alwaysConnect is on). We maintain the existing behavior that if the user has set dom.push.connection.enabled to false, we don't connect, figuring that this is the way a privacy-conscious user might indicate that they don't want to talk to "the mothership". MozReview-Commit-ID: ClbhYhnHVog
e56f7601927e35b9219957f49c27e8484a5184e4: Bug 1478410 - Fix split console close in codeMirror jsterm; r=bgrins.
Nicolas Chevobbe <nchevobbe@mozilla.com> - Wed, 25 Jul 2018 18:26:27 +0200 - rev 428673
Push 66965 by nchevobbe@mozilla.com at Fri, 27 Jul 2018 07:00:22 +0000
Bug 1478410 - Fix split console close in codeMirror jsterm; r=bgrins. This patch removes the <kbd>Esc</kbd> handler from codeMirror to put it on the jsterm-container. This prevent the interference from codeMirror when we don't need to handle the event (i.e. it should bubbles up to the toolbox where the split console state is managed). The webconsole_split test is run with both old and new jsterm. MozReview-Commit-ID: BaLyj4wSdmv
a1c1b16370154dfd42563f057fb722b37aa34112: Bug 1473209 - Ignore the click event until popup is hidden. r=birtles.
Mantaroh Yoshinaga <mantaroh@gmail.com> - Fri, 27 Jul 2018 13:38:12 +0900 - rev 428672
Push 66964 by mantaroh@gmail.com at Fri, 27 Jul 2018 06:46:51 +0000
Bug 1473209 - Ignore the click event until popup is hidden. r=birtles. The widget will hide the XUL panel when clicking to the outside of panel automatically. If a user clicks the MenuButton when opening the popup, the popup will hide automatically and mouse click event will be fired on macOS and Linux. (Windows will eat this click event since the consumeoutsideclicks of this panel is false.) As a result of it, the popup menu will be reopened. In order to prevent this, this patch will disable the MenuButton until popup is hidden by using the popuphidden event. This popuphidden event will be fired before the click event of MenuButton, then the click event of MenuButton will be fired after popuphidden immediately. MozReview-Commit-ID: 42xV0aWDmkR
84450fef88b2fa9c6696bf26cc5c211a0ce98b97: Bug 1478568 part 2: Map BLOCKQUOTE role to IA2_ROLE_BLOCK_QUOTE. r=MarcoZ
James Teh <jteh@mozilla.com> - Fri, 27 Jul 2018 10:30:25 +1000 - rev 428671
Push 66963 by mzehe@mozilla.com at Fri, 27 Jul 2018 06:01:15 +0000
Bug 1478568 part 2: Map BLOCKQUOTE role to IA2_ROLE_BLOCK_QUOTE. r=MarcoZ MozReview-Commit-ID: KxGnO0R1dRJ
08dc38b9377252d2b10caea1c10971f6fbe25908: Bug 1478568 part 1: Update IAccessible2 so we can use new roles (IA2_ROLE_BLOCK_QUOTE, etc.). r=MarcoZ
James Teh <jteh@mozilla.com> - Fri, 27 Jul 2018 10:27:44 +1000 - rev 428670
Push 66963 by mzehe@mozilla.com at Fri, 27 Jul 2018 06:01:15 +0000
Bug 1478568 part 1: Update IAccessible2 so we can use new roles (IA2_ROLE_BLOCK_QUOTE, etc.). r=MarcoZ MozReview-Commit-ID: GctgcmwrzMc
327631824cffdbec29b9b930f064575b0afbd6e1: Bug 1434579 - Fix infinite scrolling for indexedDB in storage inspector;r=miker
Julian Descottes <jdescottes@mozilla.com> - Tue, 24 Jul 2018 19:48:27 +0200 - rev 428669
Push 66962 by jdescottes@mozilla.com at Fri, 27 Jul 2018 05:55:19 +0000
Bug 1434579 - Fix infinite scrolling for indexedDB in storage inspector;r=miker MozReview-Commit-ID: 7ZyxqDPxHTK
ca5ab353b5d8e35cb757098ff4bcce04269f2101: Bug 1470176 - Implement contain:size for fieldset objects. r=dholbert
Morgan Rae Reschenberg <mreschenberg@mozilla.com> - Tue, 17 Jul 2018 13:14:39 -0700 - rev 428668
Push 66961 by rgurzau@mozilla.com at Fri, 27 Jul 2018 04:10:36 +0000
Bug 1470176 - Implement contain:size for fieldset objects. r=dholbert MozReview-Commit-ID: ImkclemDA9o
427b229b7ea4f17343d5723f10ba749b9c15cfb6: Bug 1460355 - Fix: Change how the packages are sent to the sdkmanager to install, avoid missing argument. r=nalexander
Aniket Kadam <anikadamg@gmail.com> - Tue, 24 Jul 2018 20:06:21 +0530 - rev 428667
Push 66960 by rgurzau@mozilla.com at Fri, 27 Jul 2018 04:04:53 +0000
Bug 1460355 - Fix: Change how the packages are sent to the sdkmanager to install, avoid missing argument. r=nalexander The argument --package_file was removed in the latest sdkmanager by Google's Android. But the docs for it say packages can also be sent by putting them in quotes and calling the sdk manager with them as individual args. So now instead of sending the file directly with the --package_file argument, the package names are read from the file and the sdk manager is called with them as individual args. Historically this has been thought of as a bug that happens with the wrong version of the JDK, but this can be reproduced with just java 1.8.0_181 and the most up to date version of sdkmanager currently 26.1.1 Important note, the mach bootstrap command downloads an older version of the sdk and this bug is not present in the older version. Since the way of updating packages I'm proposiing to use is backwards compatible, there shouldn't be any problem in any version of the sdkamanger. This is a simpler fix than trying the --package_file argument, particularly because it would involve capturing output (to detect this particular bug) that's also supposed to be shown to the user because this also happens when the user is supposed to be interacting with the install. MozReview-Commit-ID: L7VhCVKJNIf *** Formatting changes to satisfy the linter.
96087548d901717805a9197bcf8cc7b0d6783fb7: Bug 1475342 - Move document.getElementsByAttribute[NS] to ParentNode so it'll work for HTML document and elements;r=bz
Brian Grinstead <bgrinstead@mozilla.com> - Thu, 26 Jul 2018 13:40:13 -0700 - rev 428666
Push 66959 by bgrinstead@mozilla.com at Fri, 27 Jul 2018 04:03:35 +0000
Bug 1475342 - Move document.getElementsByAttribute[NS] to ParentNode so it'll work for HTML document and elements;r=bz It's currently only accessible on XULDocument and XULElement, but that makes porting existing JS to run in an HTML document inconvenient. We could alternatively change calling JS, but this can be easily moved and exposed in chrome contexts. MozReview-Commit-ID: JitYET20NSE
5a3702fdbd1b42a9bcac1ed5eb06889652dd04c4: Bug 1477765 - Handle rejected Promises when inspecting an object;r=jimb
Brian Grinstead <bgrinstead@mozilla.com> - Wed, 25 Jul 2018 13:16:03 -0700 - rev 428665
Push 66958 by bgrinstead@mozilla.com at Fri, 27 Jul 2018 03:58:16 +0000
Bug 1477765 - Handle rejected Promises when inspecting an object;r=jimb This changes the behavior for inspecting rejected Promises such that: (1) We don't consider them safe getters, treating them as we would a thrown exception (2) Manually handle the rejection with `catch` when possible, so that we don't create an error when trying to inspect the promise and leaving it unhandled MozReview-Commit-ID: HZL4BrjCKkA
43d426747b30b645160f4b6a7126b07896e6cfaa: Bug 1369466 - Remove the old RemotePageManager.jsm code. r=mossop
Felipe Gomes <felipc@gmail.com> - Thu, 26 Jul 2018 22:09:38 -0300 - rev 428664
Push 66957 by felipc@gmail.com at Fri, 27 Jul 2018 01:18:18 +0000
Bug 1369466 - Remove the old RemotePageManager.jsm code. r=mossop MozReview-Commit-ID: EQfA7FHG2GU
2a8afa0f67cba59bc4817851f31a791df3e3cc4b: Bug 1369466 - Move RemotePageManager test to its new location. r=mossop
Felipe Gomes <felipc@gmail.com> - Thu, 26 Jul 2018 22:09:34 -0300 - rev 428663
Push 66957 by felipc@gmail.com at Fri, 27 Jul 2018 01:18:18 +0000
Bug 1369466 - Move RemotePageManager test to its new location. r=mossop MozReview-Commit-ID: HbqFgaBWCP8
5a821925cc490c9e14dfa053c0d8e1e0347b6d12: Bug 1369466 - Remove entries related to the RemotePageManager from the startup tests whitelists. r=mossop
Felipe Gomes <felipc@gmail.com> - Thu, 26 Jul 2018 22:09:30 -0300 - rev 428662
Push 66957 by felipc@gmail.com at Fri, 27 Jul 2018 01:18:18 +0000
Bug 1369466 - Remove entries related to the RemotePageManager from the startup tests whitelists. r=mossop This is also gone from the parent process because previously it was forced to be early loaded by the fact that process-content.js also runs in the parent. Now the parent side is first initialized by the Cu.import from the Activity Stream code, which is later in the startup process MozReview-Commit-ID: FEypEi0Eemc
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip