efabe9b3a88e: Bug 1388907 - Add @mozilla.com and @testpilot- extension identifiers for SVG context-fill icons. r=jwatt, a=gchang FENNEC_56_0b3_BUILD1 FENNEC_56_0b3_RELEASE FIREFOX_56_0b3_BUILD1 FIREFOX_56_0b3_RELEASE
Jonathan Kingston <jkt@mozilla.com> - Thu, 10 Aug 2017 01:19:14 +0100 - rev 421195
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1388907 - Add @mozilla.com and @testpilot- extension identifiers for SVG context-fill icons. r=jwatt, a=gchang MozReview-Commit-ID: 7yHdgNfsrTc
dc46fc892938: Bug 1379842 - Check content principal when dragging and dropping from browser. r=smaug, a=gchang
Tooru Fujisawa <arai_a@mac.com> - Thu, 10 Aug 2017 09:43:35 +0900 - rev 421194
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1379842 - Check content principal when dragging and dropping from browser. r=smaug, a=gchang
df818e102acd: Bug 1388733 - Ensure animations resume when the image surfaces are discarded while still decoding. r=tnikkel, a=gchang
Andrew Osmond <aosmond@mozilla.com> - Wed, 09 Aug 2017 22:26:55 -0400 - rev 421193
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1388733 - Ensure animations resume when the image surfaces are discarded while still decoding. r=tnikkel, a=gchang When an animated image has been discarded, we avoided marking the composited frame invalid unless it had been previously decoded. Most of the time this was fine, but if the animated image was still decoding for the first time, then we still had a composited frame lingering that we did not mark as invalid. As a result, when we called RasterImage::LookupFrame (and indirectly FrameAnimator::GetCompositedFrame), it would always return the composited frame. This meant that RasterImage::Decode would never be called to trigger a redecode. At the same time, FrameAnimator::RequestRefresh would not cause us to advance the frame because the state was still discarded. With this patch we separate out the concepts of "has ever requested to be decoded" and "has ever completed decoding." The former is now used to control whether or not a composited frame is marked as invalid after we discover we currently have no surface for the animation -- this solves the animation remaining frozen as we now request the redecode as expected. The latter remains used to determine if we actually know the total number of frames.
36c4a1d0b3be: Bug 1386391 - Poll to check if a document has loaded rather than a definite timeout. r=smaug, a=test-only
Henry Chang <hchang@mozilla.com> - Mon, 14 Aug 2017 10:34:04 +0800 - rev 421192
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1386391 - Poll to check if a document has loaded rather than a definite timeout. r=smaug, a=test-only MozReview-Commit-ID: B293QZe3LIz
1dd09478ec89: Bug 1380512 - Fix intermittent on browser_webconsole_check_stubs_console_api. r=Honza, a=test-only
Nicolas Chevobbe <nchevobbe@mozilla.com> - Mon, 14 Aug 2017 10:30:59 +0200 - rev 421191
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1380512 - Fix intermittent on browser_webconsole_check_stubs_console_api. r=Honza, a=test-only There was an error because of the console.dir call, which is calling the server to fetch the properties of the inspected object. But, since the console.dir call was the last command to be called, the actor were cleared before the properties fetch call was done, resulting in an error on the server (no such actor for ID). To fix this, we wait for the properties fetch call to be done before closing the tab. MozReview-Commit-ID: 9bsh3vHVPVa
b6b61f8221fb: Bug 1386977 - Handle popstate events for page loads. r=automatedtester, a=test-only
Henrik Skupin <mail@hskupin.info> - Tue, 08 Aug 2017 19:48:35 +0200 - rev 421190
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1386977 - Handle popstate events for page loads. r=automatedtester, a=test-only In case of websites manipulating the browser's history via history.pushState there will be no usual page load events fired. Instead listeners for popstate events have to be used. When such an event occurs we can directly return because the browser will not load the underlying page. This only happens when navigating to another page first, or restarting Firefox. MozReview-Commit-ID: 3PceeYK9Co7
9c5b86d50b9b: Bug 1370403 - Synthesize contextmenu MouseEvent when performing webdriver actions. r=maja_zf, a=test-only
muthuraj90ec <muthuraj90ec@gmail.com> - Wed, 09 Aug 2017 07:51:18 -0400 - rev 421189
Push 7617 by ryanvm@gmail.com at 2017-08-15 14:10 +0000
Bug 1370403 - Synthesize contextmenu MouseEvent when performing webdriver actions. r=maja_zf, a=test-only MozReview-Commit-ID: 85nQTsTRttF
8b3ea08178d1: Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 6 - app update test mar files signed with a SHA384 certificate. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:54 -0700 - rev 421188
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 6 - app update test mar files signed with a SHA384 certificate. r=mhowell, a=lizzard
791e46c5e45e: Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 5 - app update test change for the new test mar file size. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:44 -0700 - rev 421187
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 5 - app update test change for the new test mar file size. r=mhowell, a=lizzard
482eab1435c1: Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 4 - app update SHA384 DER encoded certtificates. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:40 -0700 - rev 421186
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 4 - app update SHA384 DER encoded certtificates. r=mhowell, a=lizzard
a8873e18732b: Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 3 - libmar test extracted SHA384 signatures from the test mar files. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:36 -0700 - rev 421185
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 3 - libmar test extracted SHA384 signatures from the test mar files. r=mhowell, a=lizzard
b848a13d3e9a: Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 2 - libmar test mar files signed with a SHA384 cert. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:32 -0700 - rev 421184
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 2 - libmar test mar files signed with a SHA384 cert. r=mhowell, a=lizzard
cc8a7c1b2679: Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 1 - convert the libmar code from SHA1 to SHA384. r=mhowell, r=spohl, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:27 -0700 - rev 421183
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 1105689 - use SHA384 certificates to sign app update mar files. Part 1 - convert the libmar code from SHA1 to SHA384. r=mhowell, r=spohl, a=lizzard
5f9d8dc39631: Bug 641212 - use lzma compression for application update. Part 4 - app update test mar files created using lzma compression. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:14 -0700 - rev 421182
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 641212 - use lzma compression for application update. Part 4 - app update test mar files created using lzma compression. r=mhowell, a=lizzard
b51545b93e3b: Bug 641212 - use lzma compression for application update. Part 3 - test changes to support the new test mar file size and additional logging. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:05 -0700 - rev 421181
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 641212 - use lzma compression for application update. Part 3 - test changes to support the new test mar file size and additional logging. r=mhowell, a=lizzard
841c1a6eaa9c: Bug 641212 - use lzma compression for application update. Part 2 - add xe-embedded decompression support to the updater. r=mhowell, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:27:00 -0700 - rev 421180
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 641212 - use lzma compression for application update. Part 2 - add xe-embedded decompression support to the updater. r=mhowell, a=lizzard Changes to the libmar host utilities (mar and signmar) are backwards compatible with the previous versions of mar and signmar
38f2acfc18e2: Bug 641212 - use lzma compression for application update. Part 1 - xz-embedded build config changes. r=glandium, a=lizzard
Robert Strong <robert.bugzilla@gmail.com> - Sun, 30 Jul 2017 23:26:56 -0700 - rev 421179
Push 7616 by ryanvm@gmail.com at 2017-08-14 18:17 +0000
Bug 641212 - use lzma compression for application update. Part 1 - xz-embedded build config changes. r=glandium, a=lizzard
8638a6d915f3: Bug 1388805 - Export Screenshots 10.11.0 to Firefox. r=mossop, a=lizzard
Ian Bicking <ianb@colorstudy.com> - Wed, 09 Aug 2017 12:35:27 -0500 - rev 421178
Push 7615 by ryanvm@gmail.com at 2017-08-14 17:21 +0000
Bug 1388805 - Export Screenshots 10.11.0 to Firefox. r=mossop, a=lizzard MozReview-Commit-ID: Ik7V2Wd6EOO
690335e86039: Bug 1385092 - Null check for the sParserWrapper. r=alwu, a=lizzard
bechen@mozilla.com <bechen@mozilla.com> - Wed, 09 Aug 2017 17:30:52 +0800 - rev 421177
Push 7615 by ryanvm@gmail.com at 2017-08-14 17:21 +0000
Bug 1385092 - Null check for the sParserWrapper. r=alwu, a=lizzard From the crash report and code logic, it is possible that the KillClearOnShutdown comes and the NS_XPCOM_SHUTDOWN_OBSERVER_ID never comes when getting obsercerService fail. So add null check for the sParserWrapper and combine mShutdown to a new function. MozReview-Commit-ID: Cj5ph2JrO7v
572e7636edd1: Bug 1380619 - Avoid unnecessary content process leaks in SchedulerGroup dispatch during shutdown. r=mystor, a=lizzard
Nathan Froyd <froydnj@mozilla.com> - Wed, 09 Aug 2017 14:12:44 -0400 - rev 421176
Push 7615 by ryanvm@gmail.com at 2017-08-14 17:21 +0000
Bug 1380619 - Avoid unnecessary content process leaks in SchedulerGroup dispatch during shutdown. r=mystor, a=lizzard SchedulerGroup dispatch needs to replicate all the quirks of dispatching directly to threads, which means we need to handle cases where dispatch might have failed and we have resources that we don't want to leak.