64d812edc8bcdd3fb725f7fe2a93d678a21d4d18: Bug 1355273 - Allow inotify_init alongside inotify_init1. r=Alex_Gaynor,gcp a=gchang
Jed Davis <jld@mozilla.com> - Fri, 14 Apr 2017 16:17:39 -0600 - rev 396350
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1355273 - Allow inotify_init alongside inotify_init1. r=Alex_Gaynor,gcp a=gchang MozReview-Commit-ID: 5hAapLdbmeh
2adc92ca880875a4728d3499154a76fadcadfa0a: Bug 1351087 - part2 : add tests. r=sebastian a=test-only
Alastor Wu <alwu@mozilla.com> - Tue, 09 May 2017 14:10:46 +0800 - rev 396349
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1351087 - part2 : add tests. r=sebastian a=test-only Add test for handling the cases, media with silent audio track and media without audio track. MozReview-Commit-ID: 5vV9EjIjHQt
659ecca63ea66d76d26eb366030b4c43c2c6e786: Bug 1351087 - part1 : don't register agent for audio without audio track. r=baku a=gchang
Alastor Wu <alwu@mozilla.com> - Tue, 09 May 2017 14:10:43 +0800 - rev 396348
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1351087 - part1 : don't register agent for audio without audio track. r=baku a=gchang Since we don't want to show media control for media without audio track (eg. GIFV), it's no need to register audio agent for them. MozReview-Commit-ID: 22YrMkpNrcP
0241994e3aad3594cae0d42c7d80a2dff7b245e8: Bug 1340842 - Allow BrowserTestUtils.removeTab to pass options along to tabbrowser's removeTab method. r=mossop, a=test-only
Mike Conley <mconley@mozilla.com> - Fri, 17 Mar 2017 09:59:38 -0400 - rev 396347
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1340842 - Allow BrowserTestUtils.removeTab to pass options along to tabbrowser's removeTab method. r=mossop, a=test-only There were options already being passed to BrowserTestUtils.removeTab, with only a single property being observed, "dontRemove". This caused BrowserTestUtils.removeTab to return a Promise once a tab is removed, but didn't actually remove the tab (as the calling test would be responsible for that themselves). This patch removes that option, and adds a method to BrowserTestUtils called tabRemoved to use for that case instead. The options being passed to removeTab are now forwarded along directly to tabbrowser's removeTab method. MozReview-Commit-ID: JzfZuoZmlJ0
22a02cb46ff22cc1d5428e138a956e349770e4ab: Bug 1334587 - Bustage fix. r=jkt, a=bustage
Ryan VanderMeulen <ryanvm@gmail.com> - Fri, 19 May 2017 14:02:29 -0400 - rev 396346
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1334587 - Bustage fix. r=jkt, a=bustage
72da880beaeb8018297ae114eed9d7b04295f06d: Bug 1365602 - Put script blocker to nsCSSFrameConstructor::RecalcQuotesAndCounters for avoiding triggering event from nsQuoteList::RecalcAll. r=bz, a=jcristau
Xidorn Quan <me@upsuper.org> - Thu, 18 May 2017 11:25:48 +1000 - rev 396345
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1365602 - Put script blocker to nsCSSFrameConstructor::RecalcQuotesAndCounters for avoiding triggering event from nsQuoteList::RecalcAll. r=bz, a=jcristau MozReview-Commit-ID: JW0vjT0C5iU
9bbb4cd88b37f24ae7ebe42da5b99b428206f093: Bug 1363107 - Check if the startTime is set before using it in SampleAnimationForEachNode; r=hiro, a=gchang
Brian Birtles <birtles@gmail.com> - Wed, 17 May 2017 18:51:00 -0400 - rev 396344
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1363107 - Check if the startTime is set before using it in SampleAnimationForEachNode; r=hiro, a=gchang We are seeing occasional failed release assertions from calling animation.startTime().get_TimeDuration() in SampleAnimationForEachNode on Windows. My theory is that in some circumstances (perhaps graphic-driver related?) when creating a layer transaction we fail to call Layer::StartPendingAnimations and end up sending pending animations to the compositor. Prior to bug 1334583 that would have only triggered a debug assertion so it may have gone unnoticed if it depends on the system configuration. This patch makes us check that the startTime is set before we try to access it in order to avoid triggering a release-time assertion. If the startTime is not set we will use the hold time which should give us the correct behavior for a still-pending animation. (Furthermore, the holdTime is set unconditionally when we create animations so it should be correct -- but even if it were not set explicitly, its initial zero value would still likely produce a reasonable result until the start time was updated on a subsequent layer transaction. At very least, it should not crash. Likewise, if it was set to an incorrect value.) This patch also strengthens the debug assertion in SampleAnimationForEachNode to check that not only is start time not-null, but that it is set to a TimeDuration since MaybeTimeDuration also includes a third uninitialized "None" state.
e609219b9f585e3400d1c7a4f6947e6b74554766: Bug 1334587 - Fix cookie store removal and updating to use originAttributes. r=baku, a=gchang
Jonathan Kingston <jkt@mozilla.com> - Sun, 16 Apr 2017 17:58:53 +0100 - rev 396343
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1334587 - Fix cookie store removal and updating to use originAttributes. r=baku, a=gchang MozReview-Commit-ID: HpdlT4gxrl0
f43af7eb586c95d0473e98635470dca344604905: Bug 1364189 - Make sure not to retry socketTransaction if nsHttpConnectionMgr cancels it. r=mcmanus, a=gchang
Dragana Damjanovic <dd.mozilla@gmail.com> - Mon, 15 May 2017 06:20:00 -0400 - rev 396342
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1364189 - Make sure not to retry socketTransaction if nsHttpConnectionMgr cancels it. r=mcmanus, a=gchang
0a1b96abe72e99729e992daf3babf0d05262a910: Bug 1354796 - Close unconnected HTTP connection with NS_ERROR_NET_TIMEOUT after 90s timeout. r=mcmanus, a=gchang
Honza Bambas <honzab.moz@firemni.cz> - Wed, 03 May 2017 08:31:00 -0400 - rev 396341
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1354796 - Close unconnected HTTP connection with NS_ERROR_NET_TIMEOUT after 90s timeout. r=mcmanus, a=gchang
eedfc71718b4abd80fabcecf37eb122ef8aaef1a: Bug 1360095 - Wait for the window to close before checking that it does. r=Felipe, a=test-only
Blake Kaplan <mrbkap@gmail.com> - Wed, 17 May 2017 16:24:14 -0700 - rev 396340
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1360095 - Wait for the window to close before checking that it does. r=Felipe, a=test-only The external helper app service waits for a second before closing the window, which could lead to races. Also wait for the tab to close to avoid similar races, there. MozReview-Commit-ID: IdxNWRPheoY
e2018fdeb7fa5853d556ea1a864ccb54dcf4e2f4: Bug 1361983 - Extend page unload timer if flushEventLoop returns after beforeunload event. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Thu, 04 May 2017 11:53:30 +0200 - rev 396339
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1361983 - Extend page unload timer if flushEventLoop returns after beforeunload event. r=ato, a=test-only In cases when the navigation trigger function returns too late and the beforeunload event has already been fired, the page load currently gets canceled. This happens because the page unload timer hasn't been set at this time and the unbeforeunload handler doesn't extend its time. With this patch a flag is used which indicates if an beforeunload event already occurred, so when the pageunload timer notifies the page listener the unload timer can be extended to 5s as expected. MozReview-Commit-ID: FKK0oGEWijU
b99a30853f5325560cf3daf91d2b981d7e002990: Bug 1357634 - Use 'beforeunload' to detect a possible page load. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Fri, 28 Apr 2017 10:27:12 +0200 - rev 396338
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1357634 - Use 'beforeunload' to detect a possible page load. r=ato, a=test-only Using only the different unload events to detect a page load is unreliable because of a possible delay in starting the navigation, which could be triggered by a slowness of the application. By using 'beforeunload', an event will be received much earlier, and the unload timer can be extended to a couple more seconds to wait for the navigation request to start. If a website has it's own 'beforeunload' listener registered, a tab modal dialog will be opened by Firefox, and Marionette returns from the currently active command immediately to allow the test to handle the dialog. MozReview-Commit-ID: 6ZUYtFJSSnz
d880b3f5539a4f1c925f3bd26642752a1fd58f51: Bug 1357634 - Temporarily skip test_click_number_link and test_clicking_on_a_multiline_link for intermittent failures. r=Tomcat, a=test-only
Henrik Skupin <mail@hskupin.info> - Fri, 28 Apr 2017 09:00:08 +0200 - rev 396337
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1357634 - Temporarily skip test_click_number_link and test_clicking_on_a_multiline_link for intermittent failures. r=Tomcat, a=test-only MozReview-Commit-ID: 3mhV5Sf4Lvj
b4026977aaae2f3c5605fc489abefcb39041f094: Bug 1361302 - Fix clicks.html to not trigger a double navigation for history navigation. r=automatedtester, a=test-only
Henrik Skupin <mail@hskupin.info> - Tue, 02 May 2017 16:33:25 +0200 - rev 396336
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1361302 - Fix clicks.html to not trigger a double navigation for history navigation. r=automatedtester, a=test-only Our click + page load implementation doesn't handle complex navigation scenarios yet. As such those should not be triggered inside our unit tests. MozReview-Commit-ID: Cog5vohttes
0eea0b75aeb5e2257b94ac4d444934198d6a833f: Bug 1360466 - Only handle hashchange event for the current window. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Fri, 28 Apr 2017 14:16:59 +0200 - rev 396335
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1360466 - Only handle hashchange event for the current window. r=ato, a=test-only Similar to the other unload and load events during a page load, the hashchange event should only be handled if the event's target document is the current window. MozReview-Commit-ID: F1LMBh5Cy4A
e4dcd08a921c33c34d408f578e152380dd0a2844: Bug 1360466 - Use target instead of originalTarget in handleEvent. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Fri, 28 Apr 2017 17:36:42 +0200 - rev 396334
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1360466 - Use target instead of originalTarget in handleEvent. r=ato, a=test-only originalTarget seems to be outdated and not used anymore for each navigation related event. But target is, and as such handleEvent has to make use of that instead. MozReview-Commit-ID: AN2H1PbCt7A
c2d65528b868147534410064afd98cb93ac066f0: Bug 1335778 - Make element click command check for page load and wait. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Thu, 20 Apr 2017 12:12:27 +0200 - rev 396333
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1335778 - Make element click command check for page load and wait. r=ato, a=test-only If the click command triggered a page load, it should not return before the page has been fully loaded. With this patch we allow an opt-in for commands to make use of an unload check. It's set to 200ms right now, and will cancel an ongoing waitForPageLoad() if no page activity is detected. MozReview-Commit-ID: DWV53sckBS2
282d90926e0e955cc4e01e6663ba2b42af31382a: Bug 1335778 - Harden test_page_timeout_fail against intermittent failures. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Thu, 13 Apr 2017 14:57:25 +0200 - rev 396332
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1335778 - Harden test_page_timeout_fail against intermittent failures. r=ato, a=test-only Tests for page timeout durations have to use an HTTPD handler that delays or slows down document load. Otherwise there a risk that the timeout error is not returned before the document finishes loading. MozReview-Commit-ID: HGGcXfCuaSH
cc6e90e924b757209925f2605bfa4ff071f637d6: Bug 1335778 - Synchronize navigate() for trigger methods using generators. r=ato, a=test-only
Henrik Skupin <mail@hskupin.info> - Fri, 07 Apr 2017 21:44:32 +0200 - rev 396331
Push 1468 by asasaki@mozilla.com at Mon, 05 Jun 2017 19:31:07 +0000
Bug 1335778 - Synchronize navigate() for trigger methods using generators. r=ato, a=test-only In the case when the trigger callback inside navigate() uses a generator, the code has to be synchronized and needs to wait until the contained command has been completed. MozReview-Commit-ID: 8qKUMvH7HpS
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip