In order to let necko postpone the load of favicon, we have to set request context ID to the http channel that is created to load favicon.
This patch starts with passing a request context ID to nsContentUtils::LoadImage and makes other necessary changes to set the request context ID to the channel.
According to the spec, if one of the matrices for transform interpolation is
non-invertible, the used animation function must fall-back to a discrete
animation. However, in the current implementation, we always use an identity
matrix as a fallback for the non-invertible matrix.
Decompose2DMatrix and Decompose3DMatrix both return a boolean, but we just
never use it. So, in this patch, we use the returned boolean from the matrix
decomposition as a condition, and do the fallback discrete procedure for the
non-invertible matrices case.
MozReview-Commit-ID: E7i1a1MJOXN
--HG--
extra : rebase_source : 3dc9b777793dd783cd5e1c4ff750b6f8db0d2185
Android build uses cross compiler toolchain, so clang require --target option.
Also, since other options depend on NDK path, it should be set by
BINDGEN_CFLAGS environment value or bug 1397764.
MozReview-Commit-ID: 7jSSV7A5Z3q
--HG--
extra : rebase_source : f719b5130b61ffc2bd9e318103730ecbcccc185b
Now we no longer post InvalidateRenderingObservers change hint during post
traversal.
MozReview-Commit-ID: H3jJ1LKgJyV
--HG--
extra : rebase_source : 96d6bf77e6fc2b4b79882e5c7e5f43e087b56089
ServoStyleSetSizes now has two uses, one for the Stylist, and one for the UA
cache, and so the patch removes 'Stylist' from the field names.
Example output from about:memory:
> +----1,359,608 B (00.55%) -- layout
> | +----756,488 B (00.31%) -- style-sheet-cache [2]
> | +----393,968 B (00.16%) -- servo-ua-cache
> | | +--234,496 B (00.10%) -- element-and-pseudos-maps
> | | +---59,648 B (00.02%) -- revalidation-selectors
> | | +---58,320 B (00.02%) -- invalidation-map
> | | +---30,752 B (00.01%) -- other
> | | +---10,752 B (00.00%) -- precomputed-pseudos
MozReview-Commit-ID: 8oxuJO0ojp
--HG--
extra : rebase_source : 7d86216967259b71df7280261d025cc65bf00ba4
This makes "shape-outside" be able to transition between percent and pixel
shape-coordinates. This patch is similar to what bug 1266570 fixed for
"clip-path".
This will fix failures in layout/style/test/test_transitions_per_property.html
after introducing Part 4.
MozReview-Commit-ID: CAgXG39nUIl
--HG--
extra : rebase_source : 5e502a1152f780170991f0bb8c4862e6fbe244b5
This function can be used to implement animation for <basic-shape> for
shape-outside, so I remove the clip path in naming to make it more general.
MozReview-Commit-ID: LwVe0Dk5Web
--HG--
extra : rebase_source : eb0136c79b494222cca38ebd68d62f3f825bd29e
By doing this we avoid triggering assertions in the Servo code that ensure
we have registered the thread with Servo and set the proper state on it.
MozReview-Commit-ID: K6qHrYoQDLm
--HG--
extra : rebase_source : d01b0aad42273f6b92b7cfd5f5fe17ffe7b4cda0
In addition to the sourceMappingURL comment, there is a second special
comment, "sourceURL", that can be used to set the "display name" of a
style sheet for developer tools. This name is also used as the base
URL for the source-map URL resolution algorithm. sourceURL is
described here:
https://blog.getfirebug.com/2009/08/11/give-your-eval-a-name-with-sourceurl/
This patch changes Firefox to record this URL, if specified, and to
expose it (chrome-only) vai StyleSheet.webidl.
MozReview-Commit-ID: 7NwXsOf7nbY
--HG--
extra : rebase_source : bd5d25b4d44f5f220a4624db346edbc4236c9886
We have about 11,500 of these when loading gmail in a Stylo-enabled build, from
SpecifiedUrls; the objects themselves account for about 1.3 MiB of memory, and
the strings within them about 2.9 MiB.
We also have a very small number of them on the Gecko side.
The variables (basicShapeSVGBoxValues, etc.) in property_database.js are
moved to the beginning of the file so that they're defined before usage.
MozReview-Commit-ID: 7L3obIY1alP
--HG--
extra : rebase_source : 6c3dff5ecbdad8ef6cf1a49953e4ad1001620b6c
`MallocSizeOfOps::enclosing_size_of_op` is an `Option<>` type, and the panic in
question is caused by not providing a value in a case where it's needed for
measuring a HashSet.
HashMaps and HashSets are common enough that it makes sense to make
`enclosing_size_of_op` non-optional, which this patch does.
MozReview-Commit-ID: IB2aRuXHj8E
--HG--
extra : rebase_source : a6f593b718ca9e92a7a36ca7e2063a01e11c7e04
This reduces sizeof(ImageValue) from 104 to 96. When heap-allocated, this moves
it from the 112 byte bin to the 96 byte bin. Loading gmail with Stylo, there
are about 11,500 ImageValues on the heap, so this saves about 184,000 bytes.
MozReview-Commit-ID: JLe2cJ54IlL
--HG--
extra : rebase_source : 6c74d1d606db0cb1d09392f5585cc1cbadc92ebd
Sebastian Hengst
Phil Ringnalda
Wes Kocher
Kershaw Chang
J. Ryan Stinnett
Jeremy Chen
Geoff Brown
ruby
Ting-Yu Lin
Makoto Kato
Xidorn Quan
Bobby Holley
Hiroyuki Ikezoe
Nicholas Nethercote
Cameron McCormack
Jonathan Watt
Steve Fink
vincentliu
Brad Werth
Boris Chiou
Blake Kaplan
Tom Tromey
Emilio Cobos Álvarez