Commit Graph

440178 Commits

Author SHA1 Message Date
Nicholas Nethercote
ecf0b741cd Bug 1121760 (part 4) - Remove PL_DHashTableRawRemove(). r=poiru.
--HG--
extra : rebase_source : 9989b2171b8213512ce779415812fa04471fde22
2015-09-14 14:23:26 -07:00
Nicholas Nethercote
59683492e5 Bug 1121760 (part 3) - Remove PL_DHashTableRemove(). r=poiru.
--HG--
extra : rebase_source : c34d693de4aca45f2ea05c2767c8b1007c89df29
2015-09-14 14:23:24 -07:00
Nicholas Nethercote
479244f7c9 Bug 1121760 (part 2) - Remove PL_DHashTableAdd(). r=poiru.
--HG--
extra : rebase_source : 41eb939bfb5c925cba58b1af57abce9a4e5fdb30
2015-09-14 14:23:12 -07:00
Nicholas Nethercote
fcfdd8f54b Bug 1121760 (part 1) - Remove PL_DHashTableSearch(). r=poiru.
--HG--
extra : rebase_source : 770e1f49a451ecbadd778e071b204611e27cf701
2015-05-21 00:34:25 -07:00
Brian Birtles
c49da97499 Bug 1203009 part 6 - Add tests for new composite order; r=heycam 2015-09-15 13:58:17 +09:00
Brian Birtles
1bb17c4634 Bug 1203009 part 5 - Remove IsUsingCustomCompositeOrder; r=heycam 2015-09-15 13:32:12 +09:00
Brian Birtles
25e9bf79fe Bug 1203009 part 4 - Implement new composite ordering; r=heycam 2015-09-15 11:20:56 +09:00
Brian Birtles
96b49a1126 Bug 1203009 part 3 - Add mNeedsNewAnimationIndexWhenRun flag to CSSAnimation and CSSTransition; r=heycam
In the new composite order arrangement CSSAnimations and CSSTransition have the
following life-cycle:

1. Animation created by markup
   => composite order determined by markup
      (e.g. CSS animations use tree order and animation-name order;
            CSS transitions use transition trigger order)

2. Animation cancelled by changing markup
   => composite order is undefined

3. Animation is played again using the API
   => composite order is defined by when the animation is first played.
      Another way of saying this is that, at the point when the animation is
      played, it is appended to the "global animation list".

4. Animation is subsequently cancelled / played => no change

We need a way to know when we are going from 2 to 3. It would seem like we
could do that by setting mAnimationIndex to some sentinel value while it is
in 2. However, even when in 2, although the spec doesn't define the composite
order animations at this point (from an API point of view you can't access these
objects and they don't contribute to style so it doesn't need to be defined), we
sometimes will need to establish an order.

This can happen, for example, when an animation queues events and then is later
cancelled before the events are dispatched. Because we sort events based on
their associated animation at the time of dispatch (for performance reasons) we
need a deterministic order for these idle animations.

We do that (in a subsequent patch in this series) by setting mAnimationIndex
when we transition from 1 to 2. That is, these idle animations are effectively
ordered by when they became idle (which always happens in a deterministic
fashion).
2015-09-15 11:20:33 +09:00
Brian Birtles
f64b384fb1 Bug 1203009 part 2 - Remove {CSSAnimation,CSSTransition}::OwningElement() getter; r=heycam
This doesn't really save us much, but we don't need this method so we may
as well drop it.
2015-09-15 11:20:33 +09:00
Brian Birtles
3d0a063444 Bug 1203009 part 1 - Rename sequence number to animation index; r=heycam
The Web Animations specification has replaced the term "sequence number" with
references to a global animation list. This patch applies similar naming
to our animation structures.
2015-09-15 11:20:26 +09:00
Ben Kelly
0385cd5ca7 Bug 1174872 Re-enable test_fetch_basic_sw_reroute.html on mulet. a=testonly 2015-09-15 16:37:22 -07:00
Gregory Szorc
f99d0b9b59 Bug 1200461 - Prompt for Bugzilla API Key instead of password; r=smacleod
All extensions in version-control-tools should support Bugzilla API Keys
now. MozReview requires them. We'll likely remove support for passwords
and cookie auth in the future. This commit transitions the Mercurial
setup wizard to API Keys exclusively.

DONTBUILD (NPOTB)

--HG--
extra : commitid : DM33vGsljQz
extra : rebase_source : 047cd10eb976719ce94478a9a08363dbcd86ae68
2015-09-15 15:57:40 -07:00
Andrew McCreight
5446225d17 Bug 1201271 - Warn about unused results for more methods of nsTArray. r=froydnj
This leaves alone the AppendElement methods.
2015-09-15 15:30:44 -07:00
Trevor Saunders
258b34828c bug 1204070 - add a little more checking to proxy subtree removal r=davidb 2015-09-15 18:15:16 -04:00
Mats Palmgren
fd36b565c7 Bug 1204585 part 2 - [css-grid] abs.pos. child position reftests. 2015-09-15 23:34:09 +02:00
Mats Palmgren
72573926a9 Bug 1204585 part 1 - [css-grid] Use the grid area's size when converting to physical coordinates for abs.pos. items. r=dholbert
It's the item's grid area that forms the containing block rect,
not the grid container.
2015-09-15 23:34:08 +02:00
Robert Longson
0c7534f0a8 Bug 1175492 - unpref transform-origin percentage handling for SVG elements r=jwatt 2015-09-15 22:10:48 +01:00
Jonathan Kew
0a7461bd0a Bug 1202993 - Remove the logical-direction-based keywords for caption-side, and instead interpret the old physical keywords as logical sides. r=dholbert 2015-09-15 22:02:30 +01:00
Josh Aas
bccb923488 Bug 1204284: Show paper size options in OS X print dialog. r=smichaud 2015-09-15 15:40:44 -05:00
Botond Ballo
9397f8ba0b Bug 1166301 - Test that a mask layer on a fixed background of a child element is moved correctly during async scrolling. r=mstange
--HG--
extra : rebase_source : eaf1370dd62953446781ac0837a63d6d32ccaf24
extra : source : 7b415792e038c7dfbe75f27bffe2c1fec6c15b8f
2015-08-31 21:09:05 -04:00
Botond Ballo
1f87f52eb8 Bug 1166301 - When applying an async adjustment to a fixed layer, only adjust its mask layer under the same circumstances as its clip rect. r=mattwoodrow
--HG--
extra : rebase_source : 711ec4146313ffa80e52303449d2529bde2c00d0
extra : source : 1981f6bcae100a38af7dc3aa9038f74390e6ef04
2015-08-28 13:57:00 -04:00
Botond Ballo
4f8f6ce552 Bug 1166301 - Test that the clip on a fixed background of a child element is moved correctly during async scrolling. r=mstange
This also tests that regions of a fixed background layer that may be revealed by async scrolling are painted.

--HG--
extra : rebase_source : b79de765277d9ea4f23a88f923b06cbeee9712d6
extra : source : 49e72ce8143af66579c8d6c0b6a0f215e9883d5a
2015-08-28 13:34:17 -04:00
Botond Ballo
a1d5d090fe Bug 1166301 - Allow async scrolling to move the clip rects of fixed background layers. r=mattwoodrow
--HG--
extra : rebase_source : f176d9c355eeb4b7a88ca7ef3ececf03af2227cc
extra : source : 723c35828fbc080b6e372cfbbf187167db455156
2015-09-04 19:23:19 -04:00
Botond Ballo
f5f74997cd Bug 1166301 - Update an old comment in AsyncCompositionManager::AlignFixedAndStickyLayers. r=kats
--HG--
extra : rebase_source : b69104a407c62a3f25e708b172c8e51eac7e9295
extra : source : 2a98e76921bb905d750a2e36e6057a5bb6f4fd41
2015-08-28 15:21:01 -04:00
Botond Ballo
a22ee7711a Bug 1166301 - Store a flag on Layer to tell fixed background layers apart from fixed position layers. r=mattwoodrow
--HG--
extra : rebase_source : eaad2e8c7f85f20cc691353d9675611eee4733ee
extra : source : 33b55c6b3a48e3e9a2f19f498f56084d6905dfc1
2015-09-04 17:26:33 -04:00
Botond Ballo
5d157ca8b0 Bug 1166301 - Use the correct format flags for printing fixed position data in the layers dump. r=kats
--HG--
extra : rebase_source : 17752b971d1157f740e17cf4c0708c2228c0cec4
extra : source : 016c66b680b96acf5009ceefcb370d5d86660386
2015-09-04 15:57:50 -04:00
Botond Ballo
8c93a415b6 Bug 1166301 - If APZ is enabled, clip fixed background images at the layer level rather than the display item level. r=mattwoodrow
This ensures that regions beyond the clip are painted, and async scrolling can reveal them by moving the layer-level clip.

This patch also ensures that we continue creating mask layers for fixed background layers correctly, where appropriate.

--HG--
extra : rebase_source : e0759006463e7d69cd1d916c8e759b35d300a7c7
extra : source : 09922c7c550760f9b61d8ef523281234805af218
2015-09-11 20:00:22 -04:00
Botond Ballo
52a154ac58 Bug 1166301 - If APZ is enabled, only clip fixed background images to the viewport area. r=mattwoodrow
--HG--
extra : rebase_source : 9f10834ee3fe429d4afb52bce643411f385f1f1a
extra : source : 7cee3d3e42a562996fdfc602145712d21b1d91ca
2015-09-02 15:27:41 -04:00
Botond Ballo
66ecf4ccdd Bug 1166301 - Annotate fixed background layers with scroll metadata for the animated geometry root of the frame they're the background of. r=mattwoodrow
--HG--
extra : rebase_source : 0d62774bfb83070d0503ff5156bb93adc196a7de
extra : source : e90b6ffe53f1b093ca92ca39df32d873d3144704
2015-08-26 18:16:51 -04:00
Kartikaya Gupta
d726dc2234 Bug 1195436 - Fuzz scrollbar reftest failures with APZ enabled. r=mstange
In this case the test image is painted using -moz-element which layerizes
differently than not using -moz-element when APZ is enabled. This slight
layerization difference causes a few pixels to be different and the reftest
to fail. Fuzzing it seems reasonable as the fundamental nature of the test
is unchanged.

--HG--
extra : commitid : 1faZ7pEEkxj
2015-09-15 16:09:36 -04:00
Kartikaya Gupta
8e26a393f7 Bug 1200778 - Make sure to update the APZCTreeManager associated with a RenderFrameParent when it is dragged to a new window. r=mstange
--HG--
extra : commitid : FMTbYClI5hX
2015-09-15 16:09:35 -04:00
Kartikaya Gupta
7bc0f3acbb Bug 1204535 - Hoist out the code to initially compute usingDisplayPort. r=tn
--HG--
extra : commitid : 8LyyOnxNH1b
2015-09-15 16:09:35 -04:00
Kartikaya Gupta
7cd016f0fd Bug 1204535 - Relocate comment to go with the line of code it's commenting. r=tn
--HG--
extra : commitid : 6jIh8on2UNr
2015-09-15 16:09:35 -04:00
Kartikaya Gupta
a6532f54a3 Bug 1204535 - Rename usingDisplayport to usingDisplayPort for consistency. r=tn
--HG--
extra : commitid : GuYgzZK6fap
2015-09-15 16:09:35 -04:00
Kartikaya Gupta
6e406c5598 Bug 1204535 - Collapse redundant conditional block. r=tn
--HG--
extra : commitid : Av7tzi4lfaR
2015-09-15 16:09:35 -04:00
Kartikaya Gupta
7d0437c4a2 Bug 1204535 - Flatten conditional structure one level. r=tn
--HG--
extra : commitid : EcyWhZBBD2N
2015-09-15 16:09:35 -04:00
Kartikaya Gupta
4944ac2606 Bug 1204535 - Remove no-op code. r=tn
--HG--
extra : commitid : drdQpuWED0
2015-09-15 16:09:35 -04:00
David Anderson
ea934017d9 Support all blend modes in the basic compositor. (bug 1203829 part 1, r=mattwoodrow) 2015-09-15 13:07:05 -07:00
Terrence Cole
c5685d0363 Bug 1204594 - Use MOZ_RAII to replace GUARD_OBJECT where possible in the GC; r=sfink
--HG--
extra : rebase_source : 50eb4339b8fe16376c39a07978d61f6ea1f47eae
2015-09-15 12:12:26 -07:00
Benjamin Bouvier
a61f160aa5 Bug 1203297: Fix makeFrameDescriptor warnings on x86 and x64, in non-unified builds; r=terrence
--HG--
extra : commitid : 5DdCivAHE8H
extra : rebase_source : a5b4deee9fb4038458602cdb2c29e077100f1a8d
extra : amend_source : c8f18dc87a26d06c9d192eee2d3def9a2cbd6da6
2015-09-15 21:13:12 +02:00
Terrence Cole
b311e04c8f Bug 1203297 - Fix one last bit of unified bustage; r=bbouvier
--HG--
extra : rebase_source : 944d85f96c01ecf425e8f2f1c6e643bfd7341855
2015-09-15 12:10:47 -07:00
Andrew McCreight
17fe28d40c Bug 1195977, part 8 - Check that ThrowInvalidThis is passing in enough arguments. r=peterv
We have to permit passing in too many arguments because sometimes the
error is MSG_METHOD_THIS_UNWRAPPING_DENIED which only takes one
argument.
2015-09-15 11:47:04 -07:00
Andrew McCreight
bd7c5585b3 Bug 1195977, part 7 - Use variadic templates instead of var args for ThrowTypeError() and ThrowRangeError(). r=peterv
This enables type checking of these arguments.
2015-09-15 11:47:04 -07:00
Andrew McCreight
4d25fb9ee0 Bug 1195977, part 6 - Inline ErrorResult throw error methods into the header. r=peterv
This is needed to turn these into templates later.
2015-09-15 11:47:04 -07:00
Andrew McCreight
46a8a4fbb4 Bug 1195977, part 5 - Hoist out inner part of ErrorResult::ThrowErrorWithMessage() into a helper. r=peterv
This will enable us to move it to the header later, which is needed to
turn it into a template.
2015-09-15 11:47:04 -07:00
Andrew McCreight
77be143629 Bug 1195977, part 4 - Enforce number of arguments more consistently. r=peterv
The new check in ErrorResult::ReportErrorWithMessage() shouldn't be
needed and is just to protect against the possibility of another way
to construct messages being added.
2015-09-15 11:47:04 -07:00
Andrew McCreight
786ccb5a0e Bug 1195977, part 3 - Add helper for getting the number of error arguments. r=peterv 2015-09-15 11:47:04 -07:00
Andrew McCreight
53e9657f0d Bug 1195977, part 2 - Statically assert that DOM error messages don't have more arguments than the JS engine supports. r=peterv.
This makes it so that we do not need to dynamically enforce this
constraint in ErrorResult::ThrowErrorWithMessage().
2015-09-15 11:47:04 -07:00
Andrew McCreight
c4da62d679 Bug 1195977, part 1 - Add JS_EXN_TYPE to comment in Errors.msg. r=peterv 2015-09-15 11:47:03 -07:00
Terrence Cole
b5eb379da9 Bug 1203297 - Fix even more unified bustage; r=efaust
--HG--
extra : rebase_source : 483c7b420958fd38e8e3fbbb7f7be034b0792125
2015-09-09 14:26:07 -07:00