dab205ab83eb560ab7d43e2270d8355bcd2cea4b: 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 351211
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1238564 - Get rid of cross stacking context parent scroll clip. r=mattwoodrow a=lizzard MozReview-Commit-ID: JthSGAb5Kp3
9b8ac76a72bd640227e48828bebc607ece0bfde7: 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 351210
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +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
8c7f3ce9707752ed669d671fd0d6ecb76ee34f85: 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 351209
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1238564 - Include mIsAsyncScrollable information in DisplayItemScrollClip::ToString. r=roc a=lizzard MozReview-Commit-ID: 7R38KtIjM5q
c18e583d488d94bafef3e0c2e9482929b32cf81e: 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> - Tue, 23 Feb 2016 18:22:21 +0100 - rev 351208
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +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
d7db5f19e4bbd8b2a798e8ef8557afeac9695ff5: 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 351207
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +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
dceb30bcfe32475b50e18e392d2f1d2719116dc7: 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 351206
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1238564 - Allow constructing nsDisplayWrapList with a given scroll clip. r=roc a=lizzard MozReview-Commit-ID: 59FqPndU9mr
e101e6c74b7dc47ed1506b6524b3e5c0bf322b42: 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 351205
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +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
bc7308b7f1db36fd222c4499a27393e14006efe9: Bug 1216924 - Don't align to tiles (either real or virtual) if displayport suppression is enabled. r=BenWa a=ritu
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 14 Mar 2016 14:07:31 -0400 - rev 351204
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1216924 - Don't align to tiles (either real or virtual) if displayport suppression is enabled. r=BenWa a=ritu MozReview-Commit-ID: 15XWTTM0tZI
bfc3d42ce860abfbd73c8a33c043e75e4387e54a: Bug 1257499 - Fix patcher config mar-channel-ids r=nthomas a=release DONTBUILD
Rail Aliiev <rail@mozilla.com> - Thu, 17 Mar 2016 08:05:20 -0400 - rev 351203
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1257499 - Fix patcher config mar-channel-ids r=nthomas a=release DONTBUILD MozReview-Commit-ID: 1iV8GfiAmzq
bf6d2a4b10313d8a1c2e8f5fc31beee1fe62c297: Bug 1255645 - Ensure nsXULWindow constrains the window to the bounds of its screen after applying intrinsic sizing (if appropriate), by re-doing positioning after the window has been sized properly. r=emk a=ritu
Jonathan Kew <jkew@mozilla.com> - Tue, 15 Mar 2016 14:29:44 +0000 - rev 351202
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1255645 - Ensure nsXULWindow constrains the window to the bounds of its screen after applying intrinsic sizing (if appropriate), by re-doing positioning after the window has been sized properly. r=emk a=ritu
306fbf9bdddaf2290c3d51b6e19f5ada994d1863: Bug 1242449 - Fix confusion among CSS, desktop and device pixel units in nsXULWindow position/size and window staggering so as to work consistently across mixed resolution displays. r=emk a=ritu
Jonathan Kew <jkew@mozilla.com> - Tue, 01 Mar 2016 21:05:10 +0000 - rev 351201
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1242449 - Fix confusion among CSS, desktop and device pixel units in nsXULWindow position/size and window staggering so as to work consistently across mixed resolution displays. r=emk a=ritu
8971ca6f81ed53f66425011ddc1ccd3b310512ec: Bug 1255475 - Properly distinguish 'moving' from 'resizing' state when a maximized window is dragged, resulting in a WM_SIZING message followed by WM_MOVING; this allows us to handle DPI rescaling during the move if necessary. r=emk a=ritu
Jonathan Kew <jkew@mozilla.com> - Mon, 14 Mar 2016 18:35:59 +0000 - rev 351200
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1255475 - Properly distinguish 'moving' from 'resizing' state when a maximized window is dragged, resulting in a WM_SIZING message followed by WM_MOVING; this allows us to handle DPI rescaling during the move if necessary. r=emk a=ritu
7f0c41c49f0e359e27d18016665dbe2b95fd13f7: Bug 1257100 - Report we can play type 'audio/mp4; codecs=mp4a.40.29'. r=jya,a=ritu
Chris Pearce <cpearce@mozilla.com> - Wed, 16 Mar 2016 14:38:02 +0800 - rev 351199
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1257100 - Report we can play type 'audio/mp4; codecs=mp4a.40.29'. r=jya,a=ritu
c4a154a8765550da45b4a477673fcd35754f80bf: Bug 1256065. r=gerald,a=ritu
Chris Pearce <cpearce@mozilla.com> - Wed, 16 Mar 2016 13:49:26 +0800 - rev 351198
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1256065. r=gerald,a=ritu
5a5f9c53b6aa4c4ce0da90b713f6936ad1915636: Bug 1254167 - Don't allow folding to full range for atomic accesses; r=sunfish, a=lizzard
Benjamin Bouvier <benj@benj.me> - Tue, 08 Mar 2016 20:18:46 +0100 - rev 351197
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1254167 - Don't allow folding to full range for atomic accesses; r=sunfish, a=lizzard MozReview-Commit-ID: 23Gj5nV3oqq
c1af4f3c15704b3a59ee373c05bdd561beaaa177: Bug 1248822 - In LayerManagerComposite::UpdateAndRender(), call PostProcessLayers() before LayerTreeInvalidation. r=mattwoodrow, a=ritu
Botond Ballo <botond@mozilla.com> - Mon, 08 Feb 2016 19:01:45 -0500 - rev 351196
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1248822 - In LayerManagerComposite::UpdateAndRender(), call PostProcessLayers() before LayerTreeInvalidation. r=mattwoodrow, a=ritu The reason is that PostProcessLayers() can change the effective visible region, and LayerTreeInvalidation needs the final effective visible region. MozReview-Commit-ID: 1wLROyOTcIB
cd661d54ee73de897099fae295e871be31271bfe: Bug 1249600 - Lookup font and font family from font face when requesting SkTypeface. r=bas r=ritu
Mason Chang <mchang@mozilla.com> - Tue, 08 Mar 2016 07:37:16 -0800 - rev 351195
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1249600 - Lookup font and font family from font face when requesting SkTypeface. r=bas r=ritu
2fd77fb72e36e32844715012c6bae54b0e9d34aa: Bug 1249253 - "After bug 1133213, in Google Docs, screen readers started to say "blank" before characters, lines, and when navigating". r=yzenevich a=ritu
alexander <surkov.alexander> - Mon, 14 Mar 2016 11:16:00 +0100 - rev 351194
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1249253 - "After bug 1133213, in Google Docs, screen readers started to say "blank" before characters, lines, and when navigating". r=yzenevich a=ritu
112cb0b69503ef77205124328c00fcc44a2297f3: Bug 1254019 - Don't attempt to resize a maximized window on DPI change; and when handling a DPI change, constrain the resized window to the screen bounds. r=emk, a=ritu
Jonathan Kew <jkew@mozilla.com> - Tue, 15 Mar 2016 19:52:46 +0000 - rev 351193
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1254019 - Don't attempt to resize a maximized window on DPI change; and when handling a DPI change, constrain the resized window to the screen bounds. r=emk, a=ritu
8255638a3ede9da7e0cc5afb85a062330a25a677: Bug 1255127 - Decrease height of bookmark folders to match remote client item height. r=grisha, a=ritu
Chenxia Liu <liuche@mozilla.com> - Wed, 09 Mar 2016 11:48:55 -0800 - rev 351192
Push 15502 by ahunt@mozilla.com at Thu, 14 Apr 2016 20:27:48 +0000
Bug 1255127 - Decrease height of bookmark folders to match remote client item height. r=grisha, a=ritu MozReview-Commit-ID: HIveNuSTuPf
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip