Sites which are whitelisted should be allowed to autoplay audible media.
So check whether a HTMLMediaElement's owner doc's principal has an exact
"autoplay-media" permission. This ensures whitelisted origins can autoplay,
but sub-origins of whitelisted origins need their own permission.
MozReview-Commit-ID: 2IO5KIyplEa
--HG--
extra : rebase_source : 4a974aba0533bfbd5e9bb4c4c11d77d17a81db6d
For "date" I switched to using platform's DatePicker in place of our custom DateTimePicker, change that will also ensure future feature compatibility.
For "datetime" and "datetime-local" I've kept using our DateTimePicker but which will now offer spinners for selecting all fields.
MozReview-Commit-ID: 2oOORFH6OJ6
--HG--
extra : rebase_source : 0676f95e8e676c06524628d138a784e7b7290df5
When a transform thinks it's animated we should abandon screen rasterization
and instead favour local rasterization. This produces a more visually
pleasant rendering, as pixel-snapping "wobbles" the text between
frames.
The float scale of GlyphRasterSpace::Local is currently unused, but this
PR tries its best to set it to a reasonable value, based on discussion
with glennw about the intended semantics. We agreed it should specify
the scale *relative* to the parent stacking context, which means it's
just whatever scaling the stacking context's transform applies. It's
possible we'll need to clamp this value or make it properly 2-dimensional
later on.
Some book-keeping is added to StackingContextHelper to ensure that
GlyphRasterSpace::Screen is never requested by a descendent
of a stacking context using GlyphRasterSpace::Local.
nsDisplayMask is changed to use a StackingContextHelper to ensure
rasterSpace is properly propagated.
In addition, this is the first commit making use of cbindgen's new support
for bridging Rust enums natively into C++! This bumps our minimum cbindgen
to 6.0.0 (just released).
MozReview-Commit-ID: 9AlsB6nUheB
--HG--
extra : rebase_source : 247e5b197e998682cb4bb74f6f9319a9a4dd3264
The main thing to have into account is that the styleset to use is either
mLastStyleSheetSet, or mPreferredStyleSheetSet.
This last one gets set from Loader::IsAlternateSheet, which is quite nasty and
what I'm trying to remove.
MozReview-Commit-ID: BI4P1Chqtli
This regressed by bug 1435733 which didn't clear the pref in tearDown of the test, causing
following tests to still have this preference set.
MozReview-Commit-ID: n9conybbQz
--HG--
extra : rebase_source : fe0dfc7c785c18935035c7320a991edc04f3caae
This also does some minor clean up of declarations and code comments.
MozReview-Commit-ID: 31uRma7NDl8
--HG--
extra : rebase_source : 5a71c0fac5783716db5b41119b25213011895883
We plan to remove XUL persistence eventually, and this is a special case that uses the feature with an unusual attribute. This change also prevents pitfalls with getElementsByAttribute when the richlistitem descendants are made non-anonymous.
Some unneeded attributes in both the handlers and the containers richlistbox items are also cleaned up.
MozReview-Commit-ID: C05ArQGZb95
--HG--
extra : rebase_source : c5cd38498badaed8a5b8042aa906f4fbb89e47d9
The patches in this bug makes layout get more accurate values. That apparently
is confusing WebRender, which renders one more pixel height in some of the
rectangles.
I have no idea why and I couldn't repro out of the reftest harness. I suspect
something something blob invalidation, but...
MozReview-Commit-ID: A2slTJLfJBx
