5436da349c53af0dc317450d68a20bdb991626c2: Bug 1452970 - Add auto-hide option to Download toolbar icon context menu r=Gijs
Oriol Brufau <oriol-bugzilla@hotmail.com> - Sat, 14 Apr 2018 11:26:03 +0200 - rev 471799
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1452970 - Add auto-hide option to Download toolbar icon context menu r=Gijs MozReview-Commit-ID: VVPQesdzJ6
c19b8d9f4d57bce812721397d44126cba5f34fe9: Bug 1459207 - Properly style separator in Throttle drop down; r=davidwalsh
Jan Odvarko <odvarko@gmail.com> - Tue, 08 May 2018 15:21:46 +0200 - rev 471798
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1459207 - Properly style separator in Throttle drop down; r=davidwalsh MozReview-Commit-ID: 5qXoUtfqDYu
bd5d3654b01ef76ad0fe7657ec79e5738f7f65ab: Bug 1459979 - Sort artifact candidate hg revisions by local integer revision. r=froydnj
Nick Alexander <nalexander@mozilla.com> - Mon, 07 May 2018 16:06:14 -0700 - rev 471797
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1459979 - Sort artifact candidate hg revisions by local integer revision. r=froydnj This works around a situation observed with old hg versions (hg 4.2?) with mozilla-unified. I don't know why we haven't witnessed it more generally, since the sort order was textual and should have caused issues. MozReview-Commit-ID: DBtfRJ3NJGR
b66f0fade2a9a7600aee8ad2affb638f3d22ea86: bug 1457034 - populate release_partner_build_number. r=nthomas
Aki Sasaki <asasaki@mozilla.com> - Tue, 08 May 2018 19:06:31 -0700 - rev 471796
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
bug 1457034 - populate release_partner_build_number. r=nthomas MozReview-Commit-ID: EC4jHIwBWWb
929020e53bd8d712d2c32865f406ec910a352937: bug 1457034 - generate `release_partner_config` in `release_promotion` r=nthomas
Aki Sasaki <asasaki@mozilla.com> - Wed, 25 Apr 2018 15:16:49 -0700 - rev 471795
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
bug 1457034 - generate `release_partner_config` in `release_promotion` r=nthomas If we're not passed `release_partner_config` in the input, let's poll github for it in the action. MozReview-Commit-ID: 2swx76vhTE5
1c1d508a6c25743cd335ed446458013a513d8eff: bug 1457034 - re-add partner github code. r=nthomas
Aki Sasaki <asasaki@mozilla.com> - Wed, 25 Apr 2018 13:38:51 -0700 - rev 471794
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
bug 1457034 - re-add partner github code. r=nthomas We originally had this logic here, and called it from the `partner_repack` transform. This kept the config more hidden, but had the downsides of a) being difficult to test, and b) hitting the network during transforms, which we're trying to avoid. We moved this code to release-runner3, and passed in the `release_partner_config` as input, and saved it as a parameter. Parameterizing the partner config means that we can refer to it easily throughout taskgraph generation and in local testing, and we don't have to hit the network during transforms. The downsides include potentially having to generate this config in multiple places (rr3, ship-it-v2, the partner hook), and risking hitting the 20k gpg cleartext character limit in the `ACTION_INPUT` environment variable. Now I'm moving this code back into util.partners, but I'm calling it from the action, not from the transform. The action populates the `release_partner_config` parameter, so we can still access the config from anywhere in the taskgraph generation code, more easily test, and avoid hitting the network during transforms. It also means that release-runner3, ship-it-v2, and the partner hook can all use the partner config generation code from a single location, rather than having to duplicate it. Hoping this is the last major change we need to make here for a while. MozReview-Commit-ID: 8UmvmcAoZgD
5bd6b0a28492aad563e0804da8996f73e6102bd1: Bug 1089691 - Convert consumers of removePagesByTimeframe and removePagesFromHost to PlacesUtils.history.removeByFilter. r=mak
jakehm <jacob.harrowmortelliti@maine.edu> - Sun, 25 Feb 2018 14:27:03 -0500 - rev 471793
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1089691 - Convert consumers of removePagesByTimeframe and removePagesFromHost to PlacesUtils.history.removeByFilter. r=mak MozReview-Commit-ID: HevUcwPhYhd
8359164a59455e8225ba0b77a7cf9974f5d20fcd: Bug 1459118 - [wdspec] Disable test_handle_prompt_twice for execute (async) script. r=jgraham
Henrik Skupin <mail@hskupin.info> - Wed, 09 May 2018 09:41:38 +0200 - rev 471792
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1459118 - [wdspec] Disable test_handle_prompt_twice for execute (async) script. r=jgraham MozReview-Commit-ID: 4dcNUcJCur
76aad17f5b50a1b969eec8cbb5aa9875555640bc: Merge inbound to mozilla-central. a=merge
Cosmin Sabou <csabou@mozilla.com> - Wed, 09 May 2018 20:27:38 +0300 - rev 471791
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Merge inbound to mozilla-central. a=merge
2c7d7a4837461daa2f7cb65c4bcf88fce224a2bb: Bug 1446834 - Make EventStateManager to use GetFlattenedTreeParent when updating hover/active content, r=emilio
Olli Pettay <Olli.Pettay@helsinki.fi> - Wed, 09 May 2018 18:10:55 +0300 - rev 471790
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1446834 - Make EventStateManager to use GetFlattenedTreeParent when updating hover/active content, r=emilio
94652d1e109ca17c6631252c471d414e74077b38: Bug 1459728 - Include more Android test suites in try list of non-compiled suites; r=maja_zf
Geoff Brown <gbrown@mozilla.com> - Wed, 09 May 2018 07:36:53 -0600 - rev 471789
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1459728 - Include more Android test suites in try list of non-compiled suites; r=maja_zf
66c63eaf500afc42de4cc18bd056d96e26d4e160: Bug 1453454 - Improve SourceBuffer support for large encoded image data. r=jrmuizel
Andrew Osmond <aosmond@mozilla.com> - Wed, 09 May 2018 09:31:07 -0400 - rev 471788
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1453454 - Improve SourceBuffer support for large encoded image data. r=jrmuizel Regardless of the size of an encoded image, SourceBuffer::Compact would try to consolidate all of the chunks into a single chunk. If an image is quite large, it can be actively harmful to do this, because we want a very large contiguous chunk of memory for no real reason, and spend extra time on the main thread doing the memcpy/consolidation. Instead we now cap out the chunk size at 20MB. If we start allocating chunks of this size, we will not perform compacting when we have received all of the data. (Save for realloc'ing the last chunk since it probably isn't full.) On a related note, if we hit an out-of-memory condition in the middle of appending data to the SourceBuffer, we would swallow the error. This is because nsIInputStream::ReadSegments will succeed if any data was written. This leaves the SourceBuffer out of sync. We now propogate this error up properly to the higher levels. fixup
1ee5b2531836bbdb799a4dd1846430455e74ad51: Bug 1392106 - skip css writing modes on win7/debug and fix import-tests.py to support reftest_writing_modes.list. r=gbrown,xidorn
Joel Maher <jmaher@mozilla.com> - Wed, 09 May 2018 08:55:51 -0400 - rev 471787
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1392106 - skip css writing modes on win7/debug and fix import-tests.py to support reftest_writing_modes.list. r=gbrown,xidorn
18cf597d218bce788f581545819a3907e16d5884: Bug 1458004 - Link font-style values italic / oblique to the appropriate variation-font axes or synthetic styling. r=jwatt
Jonathan Kew <jkew@mozilla.com> - Wed, 09 May 2018 13:49:24 +0100 - rev 471786
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1458004 - Link font-style values italic / oblique to the appropriate variation-font axes or synthetic styling. r=jwatt
7e3488313a539b11ad1c684490c68b52f6a89349: Bug 1460258 - Re-enable discarding of animated image frames. r=aosmond
Andrew Osmond <aosmond@mozilla.com> - Wed, 09 May 2018 08:42:58 -0400 - rev 471785
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1460258 - Re-enable discarding of animated image frames. r=aosmond
e58cd9cce17f079fb964287553c49c706732833d: Bug 1458655: Do not copy DisplayItemClip onto AssignedDisplayItemData. r=mattwoodrow
Bas Schouten <bschouten@mozilla.com> - Wed, 09 May 2018 12:29:01 +0000 - rev 471784
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1458655: Do not copy DisplayItemClip onto AssignedDisplayItemData. r=mattwoodrow
ba377bd503e1a8b34dfcd15b90a3ef6289dea97d: Bug 1454149 - Do not advance animated images which are not displayed. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Wed, 09 May 2018 08:04:20 -0400 - rev 471783
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1454149 - Do not advance animated images which are not displayed. r=tnikkel All animated images on a page are currently registered with the refresh driver and advance with the tick refresh. These animations may not even be in view, and if they are large and thus cause redecoding, cause a marked increase in CPU usage for no benefit to the user. This patch adds an additional flag, mCompositedFrameRequested, to the AnimationState used by FrameAnimator. It is set to true each time the current animated image frame is requested via FrameAnimator::GetCompositedFrame. It is set to false each time the frame is advanced in FrameAnimator::AdvanceFrame (via FrameAnimator::RequestRefresh). If it is true when FrameAnimator::RequestRefresh is called, then it will advance the animation according to the normal rules. If it is false, then it will set the current animation time to the current time instead of advancing. This should not cause the animation to fall behind anymore or skip frames more than it does today. This is because if FrameAnimator::GetCompositedFrame is not called, then the internal state of the animation is advancing ahead of what the user sees. Once it is called, the new frame is far ahead of the previously displayed frame. The only difference now is that we will display the previous frame for slightly longer until the next refresh tick. Note that if an animated image is layerized (should not happen today) or otherwise uses an ImageContainer, this optimization fails. While we know whether or not we have an image container, we do not know if anything is actively using it.
17ba1a71265a2552c810db082658b9741c5e1051: Bug 1460054 - Update Debugger Frontend v49. r=jdescottes
Jason Laster <jason.laster.11@gmail.com> - Wed, 09 May 2018 13:43:46 +0200 - rev 471782
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1460054 - Update Debugger Frontend v49. r=jdescottes MozReview-Commit-ID: 4wr5NnLBTn7
eeaae6812d825fad8bb92be7f496f74952d82654: Bug 1302449 - Remove the "referrer" directive in CSP, r=ckerschb
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 09 May 2018 13:15:08 +0200 - rev 471781
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1302449 - Remove the "referrer" directive in CSP, r=ckerschb
754f3238cab94d87047ed44daa1b8e1e99a9e1c5: Bug 1400678 - quota storage should be cleared on exit if user has requested cookies to be cleared on exit - fix a ES failure, r=me CLOSED TREE
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 09 May 2018 11:59:15 +0200 - rev 471780
Push 9374 by jlund@mozilla.com at Mon, 18 Jun 2018 21:43:20 +0000
Bug 1400678 - quota storage should be cleared on exit if user has requested cookies to be cleared on exit - fix a ES failure, r=me CLOSED TREE
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip