ffd3366e43f3e7fed749596dfacdb366d38e61ca: Bug 1531532: Remove incorrect reftest fuzzy annotation. r=bustage
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 05 Mar 2019 18:36:39 +1300 - rev 520223
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1531532: Remove incorrect reftest fuzzy annotation. r=bustage
2858e470c2bcaa361b6809158921b01ed0f12d93: Merge mozilla-central to mozilla-inbound. a=merge CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Tue, 05 Mar 2019 06:24:16 +0200 - rev 520222
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Merge mozilla-central to mozilla-inbound. a=merge CLOSED TREE
20d6f233678b8cbbfec09f85c40ae42e21263a72: Bug 1495170. Use CreateClippedDrawTarget more. r=mstange
Jeff Muizelaar <jrmuizel@gmail.com> - Mon, 04 Mar 2019 22:30:09 -0500 - rev 520221
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1495170. Use CreateClippedDrawTarget more. r=mstange This lets us restrict the size of the mask surface that we allocate to the destination tile size. This gives a large performance improvement. It also includes some miscelanous fixes to the CreateClippedDrawTarget code path. Differential Revision: https://phabricator.services.mozilla.com/D21750
df0f64d6ae61e707d451d6ab0443e00ef2fbf8b9: Bug 1495170. Handle mask offsets.
Jeff Muizelaar <jrmuizel@gmail.com> - Mon, 04 Mar 2019 22:30:08 -0500 - rev 520220
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1495170. Handle mask offsets. Differential Revision: https://phabricator.services.mozilla.com/D21749
10304db77c0ac3ffc62fa2355999706c499b3252: Bug 1531532. Use preTranslate instead of postTranslate when correcting for the mask offset. r=mattwoodrow
Jeff Muizelaar <jrmuizel@gmail.com> - Mon, 04 Mar 2019 22:30:06 -0500 - rev 520219
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1531532. Use preTranslate instead of postTranslate when correcting for the mask offset. r=mattwoodrow DTO = DrawTargetOffset = (-Origin.x, -Origin.y) CTM = CurrentTransform MASKT = MaskTransform = Inv(CurrentTransform) MASKO = MaskOffset = (GetRect().x, GetRect().y) The transform to device space is: MASKT * CTM * DTO Currently we do: MASKT = MASKT * MASKO Which gives us MASKT * MASKO * CTM * DTO. This works fine if there's no scale but will not properly cancel out if there is. I believe we want: MASKO * MASKT * CTM * DTO To get this we need to preTranslate instead of postTranslate. Differential Revision: https://phabricator.services.mozilla.com/D21604
f4e9e5429fd82f9c3787ca2d42798a2bf3d353f9: Bug 1532005 - Implement a new js/public/ArrayBuffer.h header to centralize functionality for creating and interacting with ArrayBuffers. r=sfink
Jeff Walden <jwalden@mit.edu> - Mon, 04 Mar 2019 15:19:16 -0800 - rev 520218
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1532005 - Implement a new js/public/ArrayBuffer.h header to centralize functionality for creating and interacting with ArrayBuffers. r=sfink Differential Revision: https://phabricator.services.mozilla.com/D21827
27986829a1604fbbdcdaf8fbfb2ab7f8f1310bc0: Bug 1487113 - MOZ_RELEASE_ASSERT existing implicit assumption about alt-data Write() in ScriptLoader.cpp (r=baku)
Luke Wagner <luke@mozilla.com> - Mon, 04 Mar 2019 19:38:13 -0600 - rev 520217
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1487113 - MOZ_RELEASE_ASSERT existing implicit assumption about alt-data Write() in ScriptLoader.cpp (r=baku)
0c4c0810b93fa8fb8c8f1439b78ced96ba91450f: Bug 1463347 - Add distinction between timeLog and timeEnd messages r=nchevobbe
bomisore <solaocodes@gmail.com> - Mon, 04 Mar 2019 17:12:47 +0000 - rev 520216
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1463347 - Add distinction between timeLog and timeEnd messages r=nchevobbe Differential Revision: https://phabricator.services.mozilla.com/D21306
a76b23d70349b38dfa885987c6888c730ede4173: Bug 1527210 - Drop KeyframeEffect::MaybeUpdateFrameForCompositor; r=hiro
Brian Birtles <birtles@gmail.com> - Tue, 05 Mar 2019 03:09:48 +0000 - rev 520215
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1527210 - Drop KeyframeEffect::MaybeUpdateFrameForCompositor; r=hiro Since bug 1524480 we set the NS_FRAME_MAY_BE_TRANSFORMED frame bit when needed in RestyleManager::ProcessRestyledFrames so that it is now redundant to also set it from KeyframeEffect. Furthermore, setting frame bits from KeyframeEffect is a little fragile since it depends on the life cycle of the KeyframeEffect which is independent of the nsFrame. If we can avoid doing that, we probably should. Differential Revision: https://phabricator.services.mozilla.com/D21885
211f6573535bdc2721960b2e1339ba9069a2ae4e: Bug 1527210 - Fix handling of animation of opacity on display:table; r=hiro
Brian Birtles <birtles@gmail.com> - Tue, 05 Mar 2019 03:09:33 +0000 - rev 520214
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1527210 - Fix handling of animation of opacity on display:table; r=hiro As with the previous patch in this series, we need to pay particular attention to how we handle display:table content when detecting animations on a element. Please see the extended description in that patch for an explanation of different frame types involved. As with transforms, our handling of opacity is also inconsistent. In particular, we fail to return true from nsIFrame::HasOpacityInternal for display:table content with opacity animations applied due to the conflicting requirements for a primary frame and having opacity animations (which are stored on the style frame). Unlike transforms, however, we do not inherit the opacity to the table wrapper. Instead we leave it on the inner table frame. As a result, we should not check for a primary frame, but instead we should check for the style frame for the primary frame. This patch adjusts this handling to check instead for the appropriate style frame as opposed to requiring a primary frame. It includes a reftest that fails without the code changes in this patch. Differential Revision: https://phabricator.services.mozilla.com/D21884
5cf9e494f69061f8b31fde9ba7dc2108877f1650: Bug 1527210 - Be more consistent about only applying transforms to primary frames; r=hiro
Brian Birtles <birtles@gmail.com> - Tue, 05 Mar 2019 03:09:19 +0000 - rev 520213
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1527210 - Be more consistent about only applying transforms to primary frames; r=hiro For display:table content we generate two frames: a table wrapper frame and an inner table frame. The styles are applied to the inner frame (referred to as the style frame), whilst the wrapper frame is the primary frame for the content. However, in order to make tables with transforms behave as a container for abspos/fixed-pos content as required by the spec, we apply the transform to the wrapper frame (bug 722777) by inheriting the transform from inner to wrapper and then ignoring the transform on the inner frame (bug 722777 and bug 816458). When handling animations on table elements we need to be careful of this distinction. in particular, css animations[1] and web animations[2] require that when we have an unfinished transform animation targetting an element, the element acts as if it had `will-change: transform` applied and therefore generates a stacking context. As a result we need to accurately detect when a frame should be considered as having transform animations applied to it or not for the purpose of creating a stacking context. Previously our handling of display:table content was quite inconsistent and contradictory. For example, `nsIFrame::HasAnimationOfTransform` would check for a primary frame AND for animations on that frame, despite the fact that we only ever store animations on the style frame. As a result it could never return true for either a table wrapper or inner table frame. This patch attempts to make this handling at least a little more consistent, producing the following result: Outer table frame (primary frame): nsIFrame::IsTransformed → true nsIFrame::IsCSSTransformed → true nsIFrame::HasAnimationOfTransform → true nsLayoutUtils::HasAnimationOfProperty(frame, eCSSProperty_transform) → false Inner table frame (style frame): nsIFrame::IsTransformed → false nsIFrame::IsCSSTransformed → false nsIFrame::HasAnimationOfTransform → false nsLayoutUtils::HasAnimationOfProperty(frame, eCSSProperty_transform) → true We maintain that the NS_FRAME_MAY_BE_TRANSFORMED bit is only set on the primary frame whilst the mMayHaveTransformAnimation flag is only set on the style frame. Note that we don't simply always put everything on the primary frame because for other property types (e.g. opacity) the default setup of putting all styles and animations on the style frame is simpler and correct. So far it is only transforms that require special handling to apply the effect to the wrapper frame. This patch adds a reftest that fails without the code changes included in this patch. [1] https://drafts.csswg.org/css-animations/#animations [2] https://drafts.csswg.org/web-animations-1/#side-effects-section Differential Revision: https://phabricator.services.mozilla.com/D21883
71df482164471a59a54d9531e34dedec05bb9b70: Merge mozilla-central to autoland. a=merge CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Tue, 05 Mar 2019 06:22:50 +0200 - rev 520212
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
28d928686e97f9d194b7794505d1a48008572e57: Bug 1532226 - Move observers registration for Fluent DOM to C++. r=smaug
Zibi Braniecki <zbraniecki@mozilla.com> - Tue, 05 Mar 2019 02:16:14 +0000 - rev 520211
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1532226 - Move observers registration for Fluent DOM to C++. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D21898
c6d34d35ff2e0260924c8d870aef76cea034f487: Bug 1530801 - Replace waitForCondition in browser_947914_button_addons.js withTestUtils.waitForCondition r=johannh
Mellina Yonashiro <yonashiro.mellina@gmail.com> - Mon, 04 Mar 2019 21:36:02 +0000 - rev 520210
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1530801 - Replace waitForCondition in browser_947914_button_addons.js withTestUtils.waitForCondition r=johannh waitForCondition usage in the browser_947914_button_addons.js test file can be replaced by the TestUtils.waitForCondition utility function. > The function was replaced. There was only one occurance in this file (browser_947914_button_addons.js), but may exists in other ones. Differential Revision: https://phabricator.services.mozilla.com/D21720
07c49703b70c4cd01985771942e84aa37a66663c: Bug 1530220 - part4 : separate tesing web audio with gum to another test. r=cpearce
Alastor Wu <alwu@mozilla.com> - Tue, 05 Mar 2019 02:13:55 +0000 - rev 520209
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1530220 - part4 : separate tesing web audio with gum to another test. r=cpearce Testing web audio with GUM is not related with the original purpose of this test. In order to reduce the complexity of this test, separate this part as another new test. Also modify the naming of functions, because Mozilla coding style is to use the camelCase for the name. Differential Revision: https://phabricator.services.mozilla.com/D21257
9ce43f1e7bc080fe10b9b631c7501bc95cd87939: Bug 1530220 - part3 : speed up test. r=padenot
Alastor Wu <alwu@mozilla.com> - Fri, 01 Mar 2019 10:00:40 +0000 - rev 520208
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1530220 - part3 : speed up test. r=padenot We can listen for the `block` event to know whether AudioContext hasn't started yet which can speed up the test. Differential Revision: https://phabricator.services.mozilla.com/D21256
f706441a86b530d30be4fba47bff43f96ade97cb: Bug 1530220 - part2 : modify test in order to test different kinds of keycode. r=cpearce
Alastor Wu <alwu@mozilla.com> - Tue, 05 Mar 2019 02:09:50 +0000 - rev 520207
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1530220 - part2 : modify test in order to test different kinds of keycode. r=cpearce Except printable keys, we would treat `carriage return` and `space` as supported user gesture inputs for activating document. Other keys won't activate document. Differential Revision: https://phabricator.services.mozilla.com/D21255
7c1b053e161b0795c83fc39289a8d4335b146127: Bug 1530220 - part1 : allow some non-printalble keys as supported user gesture inputs to activate document. r=masayuki,cpearce
Alastor Wu <alwu@mozilla.com> - Tue, 05 Mar 2019 02:06:22 +0000 - rev 520206
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1530220 - part1 : allow some non-printalble keys as supported user gesture inputs to activate document. r=masayuki,cpearce `carriage return` and `space` are common keys which user might use to start media, so we should take account them as supported user gesture inputs. As their pseudo char code are zero, we have to check their key code in order to distinguish them from other controls keys such as shift, alt... Differential Revision: https://phabricator.services.mozilla.com/D21253
5d76e6e7025c4a7b26aa95b60ae54fcc713e78a6: Bug 1531259: Avoid to shrink buttons open inspector. r=pbro
Daisuke Akatsuka <dakatsuka@mozilla.com> - Tue, 05 Mar 2019 01:04:31 +0000 - rev 520205
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Bug 1531259: Avoid to shrink buttons open inspector. r=pbro Differential Revision: https://phabricator.services.mozilla.com/D21638
c59f0f40e0f6995c2bf70499e783afc7626cab96: Merge inbound to mozilla-central. a=merge
Ciure Andrei <aciure@mozilla.com> - Tue, 05 Mar 2019 06:20:52 +0200 - rev 520204
Push 10862 by ffxbld-merge at Mon, 11 Mar 2019 13:01:11 +0000
Merge inbound to mozilla-central. a=merge
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip