f1720d53bfc72bb7d71263aba9ab744db7c6c77c: Automatic version bump. CLOSED TREE NO BUG a=release
ffxbld <release@mozilla.com> - Fri, 18 Mar 2016 17:30:01 -0700 - rev 342623
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Automatic version bump. CLOSED TREE NO BUG a=release
24b6aaac8973e7a690fec928395977d194079257: Bug 1247854 - Apply the correct scroll clips to the nsDisplayTransform and nsDisplayPerspective of a scrolled perspective item. r=mattwoodrow a=ritu
Markus Stange <mstange@themasta.com> - Fri, 26 Feb 2016 01:29:41 +0100 - rev 342622
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1247854 - Apply the correct scroll clips to the nsDisplayTransform and nsDisplayPerspective of a scrolled perspective item. r=mattwoodrow a=ritu I've decided to fix this in a very explicit way. The only "magic" part that's left is how we decide that the AGR of the perspective item is outside the scrolled frame (and I'm not sure myself how that works). I didn't want to change what scroll clips we set on what items, because the scroll clip really belongs on the perspective item, because that's the item that needs to be clipped, and it should also be the item that should be scrolled if it weren't for the fact that APZ wouldn't know that it should apply the perspective transform before the APZ transform. MozReview-Commit-ID: BBw8VPohQI4
8ec449c9ddb13b94576d4306468839d999024b15: Bug 1238564 - Get rid of cross stacking context parent scroll clip. r=mattwoodrow a=lizzard
Markus Stange <mstange@themasta.com> - Fri, 04 Mar 2016 14:49:35 -0500 - rev 342621
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - Get rid of cross stacking context parent scroll clip. r=mattwoodrow a=lizzard MozReview-Commit-ID: JthSGAb5Kp3
f0a8c4bbf0966cd72634e1f5f8887c3e321a8648: Bug 1238564 - Don't do another pass over the display list to figure out ancestor scroll clips. r=mattwoodrow a=lizzard
Markus Stange <mstange@themasta.com> - Sat, 05 Mar 2016 11:27:54 -0500 - rev 342620
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - Don't do another pass over the display list to figure out ancestor scroll clips. r=mattwoodrow a=lizzard MozReview-Commit-ID: BgySqVGG43R
9a8955f2e94f47fe6d90703341fa7ad0d8a31ed9: Bug 1238564 - Include mIsAsyncScrollable information in DisplayItemScrollClip::ToString. r=roc a=lizzard
Markus Stange <mstange@themasta.com> - Wed, 24 Feb 2016 16:23:32 +0100 - rev 342619
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - Include mIsAsyncScrollable information in DisplayItemScrollClip::ToString. r=roc a=lizzard MozReview-Commit-ID: 7R38KtIjM5q
a61aaa2d0ac76254234f3f29da4c753f5bcf0070: Bug 1238564 - When building a fixed/sticky display item, don't restore the clip until we're ready to build that item so that inner items aren't unnecessarily clipped. r=roc a=lizzard
Markus Stange <mstange@themasta.com> - Fri, 18 Mar 2016 15:38:40 -0400 - rev 342618
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - When building a fixed/sticky display item, don't restore the clip until we're ready to build that item so that inner items aren't unnecessarily clipped. r=roc a=lizzard This isn't really about regular clips, it's about scroll clips. If the inner item has an unnecessary scroll clip (one that's already on the parent), this can cause the inner item's bounds to be larger than necessary because, after the first patch in bug 1238564, it will include the whole bounds of async-scrollable scroll frames. Also, if e.g. the inner item is an opacity item, and it has a scroll clip that's not just the innermost ancestor scroll clip of all of its children, then FrameLayerBuilder's mContainerBounds == mAccumulatedChildBounds assertion can fail if the opacity item gets flattened away, because the child bounds won't have been enlarged for the scroll clip. There must be a better way to do the clip resetting in nsFrame::BuildDisplayListForStackingContext - the code is not pretty at all. But I'd rather get the tests passing first before we figure out how to clean it up. MozReview-Commit-ID: E1DdpN546va
28505a320d5e6f7378ca783564ff1e5eb9a8768f: Bug 1238564 - Set the innermost possible scroll clip on opacity items during creation. r=mattwoodrow a=lizzard
Markus Stange <mstange@themasta.com> - Fri, 04 Mar 2016 15:05:58 -0500 - rev 342617
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - Set the innermost possible scroll clip on opacity items during creation. r=mattwoodrow a=lizzard Always use an ancestor scroll clip of all direct children, or the original scroll clip if the children don't share the same scroll clip tree. Unfortunately this requires another pass over the stacking context display list. Also, fix clips, scroll clips and creation order of blend items: If a clipped mix-blend-mode item contains absolute / fixed positioned items, those items should not be clipped, same for blend container items. When a transform item contains blend modes, create the blend container inside the transform. Don't do tree comparisons on scroll clips from different scroll clip trees. If the inner scroll clip is nullptr, because it was cleared, it will look like it's the ancestor of the outer non-nullptr scroll clip. These changes don't look very related, but it was very hard to get tests passing with only some of the changes and not the others, and after having spent two weeks on this patch I'm not thrilled about going back and checking exactly which change was necessary to fix which test failure. MozReview-Commit-ID: IKGciUBrdNa
b6ba21bf67fc2a4844de6fb8b3774dc3d6ef0623: Bug 1238564 - Allow constructing nsDisplayWrapList with a given scroll clip. r=roc a=lizzard
Markus Stange <mstange@themasta.com> - Fri, 26 Feb 2016 13:38:12 +0100 - rev 342616
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - Allow constructing nsDisplayWrapList with a given scroll clip. r=roc a=lizzard MozReview-Commit-ID: 59FqPndU9mr
38b65261b8a3dad90c458323e44a529f382bf6ae: Bug 1238564 - Anticipate async scrolling when computing the scroll clipped bounds of a display list. r=roc a=lizzard
Markus Stange <mstange@themasta.com> - Mon, 22 Feb 2016 16:17:16 +0100 - rev 342615
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1238564 - Anticipate async scrolling when computing the scroll clipped bounds of a display list. r=roc a=lizzard This makes sure that for example the bounds of an opacity item are not empty if the opacity item contains a scroll frame whose contents are currently scrolled offscreen but still inside that scroll frame's display port. On its own, this changeset causes test failures due to missed optimizations because the bounds of many opacity items are now too large. That's because of the way we're setting scroll clips on opacity items at the moment: Even if the opacity is inside a scroll frame, we're currently only setting that scroll frame's scroll clip on the opacity item's contents, not on the opacity item itself, because the opacity item might also contain other items that are not scrolled by this scroll frame. The next patch in this bug will make us only do that when necessary. MozReview-Commit-ID: 9TtcJ7eQE7U
69d2eab7852f0cb27127f3937be146c3b4e8b575: Fold nsDisplayBlendContainer constructors. (bug 1209278 part 3, r=mstange, a=lizzard)
David Anderson <danderson@mozilla.com> - Mon, 29 Feb 2016 01:45:43 -0500 - rev 342614
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Fold nsDisplayBlendContainer constructors. (bug 1209278 part 3, r=mstange, a=lizzard) MozReview-Commit-ID: HuHQuVGrloS
4315f192ec3a68466776a4939e9f327a55714018: Remove lazy scrollinfo hoisting introduced in bug 1193557. (bug 1209278 part 2, r=mstange, a=lizzard)
David Anderson <danderson@mozilla.com> - Tue, 23 Feb 2016 10:11:43 -0800 - rev 342613
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Remove lazy scrollinfo hoisting introduced in bug 1193557. (bug 1209278 part 2, r=mstange, a=lizzard) MozReview-Commit-ID: lzGTOnGYOy
9133a529cbcd6f540c7dc980ffc11bae6781d941: Require mix-blend mode support in all compositors and layer managers. (bug 1209278 part 1, r=mstange, a=lizzard)
David Anderson <danderson@mozilla.com> - Tue, 23 Feb 2016 10:11:21 -0800 - rev 342612
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Require mix-blend mode support in all compositors and layer managers. (bug 1209278 part 1, r=mstange, a=lizzard) MozReview-Commit-ID: 5mnBXW8dRrD
4c7b6e5d1b619d47f799b4d90bd83ab8bcd215b6: Bug 1254721: Ensure consistency between Cenc offsets and sizes table. r=gerald a=lizzard
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 15 Mar 2016 16:34:33 +1100 - rev 342611
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1254721: Ensure consistency between Cenc offsets and sizes table. r=gerald a=lizzard MozReview-Commit-ID: E1KbKIIBR87
36191ebd2e850016318e90ff29c315a4f460ae2a: Bug 1250669. Don't init dwrite fonts if content device creation fails. r=dvander a=lizzard
Wes Kocher <wkocher@mozilla.com> - Fri, 18 Mar 2016 11:50:46 -0700 - rev 342610
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1250669. Don't init dwrite fonts if content device creation fails. r=dvander a=lizzard MozReview-Commit-ID: CyA7FzpInlS
5ff7037205e4f496928fa9a9141b19264aa97be5: Bug 1255918 - Disable youtube flash rewriting on beta 46; r=cpeterson, a=lizzard
Kyle Machulis <kyle@nonpolynomial.com> - Tue, 15 Mar 2016 10:14:00 +0100 - rev 342609
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1255918 - Disable youtube flash rewriting on beta 46; r=cpeterson, a=lizzard
91661ec6d973529f2ddfc02a6f06eb8321714e23: Bug 1242724: add an export of runnable_utils.h unless/until it gets moved to xpcom/mfbt r=glandium, a=lizzard
Randell Jesup <rjesup@jesup.org> - Thu, 18 Feb 2016 11:44:55 -0500 - rev 342608
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1242724: add an export of runnable_utils.h unless/until it gets moved to xpcom/mfbt r=glandium, a=lizzard MozReview-Commit-ID: C577TmkWaWE
56f6fe01291fc629a8bf7137ef8e07e541413955: Bug 518805 - Don't do meta refreshes when backgrounded. r=bz, a=lizzard
James Willcox <snorp@snorp.net> - Wed, 02 Mar 2016 16:20:48 -0600 - rev 342607
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 518805 - Don't do meta refreshes when backgrounded. r=bz, a=lizzard This is controlled by browser.meta_refresh_when_inactive.disabled, which is false (allow refreshes) on desktop, and true (disable refreshes) on Fennec
0de4101e6ef67cad22e471f0ca8145160a4b2cc7: Bug 1232651 - don't show search suggestions in private browsing r=mcomella, a=lizzard
Andrzej Hunt <ahunt@mozilla.com> - Wed, 06 Jan 2016 15:43:13 -0800 - rev 342606
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1232651 - don't show search suggestions in private browsing r=mcomella, a=lizzard We also remove the special case for updating mSuggestClient when search engines are modified during private browsing - this causes a weird edge case where we potentially show history suggestions after switching search engines (this seems to be because having mSuggestClient == null avoids us even reaching the stage where we usually recycle unneeded suggestions).
4929e9426cc4813b4b653fbe42093d56ad84e4a4: Bug 1251894 - In CompositorD3D11::CreateTexture, copy as much as the render target allows. r=bas, a=ritu
Markus Stange <mstange@themasta.com> - Thu, 10 Mar 2016 16:03:24 -0500 - rev 342605
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1251894 - In CompositorD3D11::CreateTexture, copy as much as the render target allows. r=bas, a=ritu MozReview-Commit-ID: KK5wu3T4tLE
2d8efe1a5bd6afcf4361580bec221fd054cdaad0: Bug 1249418 - Update illustration image of Sync slide. r=ahunt, a=ritu
Chenxia Liu <liuche@mozilla.com> - Tue, 15 Mar 2016 12:30:09 -0700 - rev 342604
Push 13430 by rjesup@wgate.com at Sun, 20 Mar 2016 05:01:22 +0000
Bug 1249418 - Update illustration image of Sync slide. r=ahunt, a=ritu MozReview-Commit-ID: LW5SgnnkA95
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip