Also set <menu>.type's default value as "toolbar" and
remove HTMLButtonElement.menu per HTML spec.
MozReview-Commit-ID: jE6TmmvWa5
--HG--
extra : rebase_source : f0ded9a69055777b9430aeb91b53fef1a43af8e0
Several mochitests call `assertSnapshots`, which prints a reftest-like output
for use with the reftest analyzer. Update these lines to check failure patterns
before printing, like the regular assertion methods do.
MozReview-Commit-ID: CfChoar7bp8
Create an extra style context using the visited values (if they exist). This
mirrors the logic Gecko performs in nsStyleSet::GetContext for visited support.
MozReview-Commit-ID: EiJQXDgz8tX
Rename and duplicate a crashtest to better cover each variation of a single
:link or single :visited style on a pseudo-element.
MozReview-Commit-ID: JMFXD7nk9fH
While studying `GetContentStateForVisitedHandling` for adaptation to Stylo, I
noticed it calls through to `GetContentState`, which depends on external state
such as private browser, etc.
However, there's no need to call `GetContentState` here since this function
always clears both unvisited and visited if either is set.
MozReview-Commit-ID: JLwKnowQbJ2
On the main thread, we use Servo backend, and the type of computed::Length is
|app_units::Au| (i.e. i32).
However, on the compositor thread, we use Gecko backend, and the type of
the length in nsCSSValue is |float|, so there might be some difference.
Use "0.5 / 60" because we round the interpolated result to the nearest
integer, and convert it into an app unit value, so the tolerance could be
this value.
MozReview-Commit-ID: EBceiO7keH1
--HG--
extra : rebase_source : aa4e3ac68fed1bcbdb51d93b403a15b0304c144d
We get the progress as |double|, and then pass it to a function by a |float|
type, and then finally cast it back to |double| for the interpolation.
We should avoid casting it back and forth, so change the function argument to
use |double| type for the progress.
MozReview-Commit-ID: 7QzfVBC7hSt
--HG--
extra : rebase_source : 62467bf0a734b650f524af656658cdfdabca2a5c
The ignore-root-scroll-frame flag is generally needed on Fennec, or possibly
other zoom-enabled platforms, when we have them. It allows hit-testing things
outside the main thread's notion of what is visible, because that might occur
when the user zooms out.
For largely historical reasons, we are passing this flag around in other scenarios,
such as when doing hit-tests for touch events, because in the past touch events
and zooming only happened on Fennec, so it didn't matter. Now that we have
touch events enabled on other platforms, such as Windows, we need to make the
distinction clearer.
MozReview-Commit-ID: BlHjtjFYgzv
--HG--
extra : rebase_source : cbfeab4666b5556ba0b38f3abdf666d63945b9a1
Add a Send to Device subview to the page action panel. When the page isn't
sendable, disable the Send to Device menu item. When the user doesn't have any
devices, show a menu item that opens the Firefox Account preferences pane.
Generalize gSync.populateSendTabToDevicesMenu() so that it can be used to
populate any kind of container, not only a menupopup with menuitems.
Add an SVG that shows a phone and an SVG that shows a desktop.
MozReview-Commit-ID: EZQKAEAr08q
--HG--
extra : rebase_source : bda87f105712a6c6ba83da1a78179eee93b5f4d0
When the counter style in the style struct changes, CalcDifference
would return ReconstructFrame, which should cause corresponding use
node to be reconstructed. That means a use node with retired counter
style should always be destroyed in the next flush, so it makes no
sense to reset them anymore.
However, we would still need to mark counter lists dirty because
otherwise their content may not get update when there are changes to
counter styles which are still valid.
MozReview-Commit-ID: FnBPx81StzG
--HG--
extra : rebase_source : 2adf7b64484746a5f416b7902df2ac718a3fdeab
This is the Servo side change for [bug 1366735](https://bugzilla.mozilla.org/show_bug.cgi?id=1366735).
Source-Repo: https://github.com/servo/servo
Source-Revision: e457d22f81ac0f45c4dc96867162f276de7bd291
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 8ba04dab52e5c46e1719988c5ae9deda17a67a5a
A previous bug missed a few places where we could theoretically
reenter the CC.
MozReview-Commit-ID: I0otlAEwyZa
--HG--
extra : rebase_source : 064b127a2c28a52b2807cd78031de9af4f258f60
If we had an unsuccessful build, then duplicating the warnings at the
end of the compilation job would just be burying the actual error in a
blizzard of noise.
btian
Hiroyuki Ikezoe
J. Ryan Stinnett
Boris Chiou
Kartikaya Gupta
Mantaroh Yoshinaga
Tom Tromey
Drew Willcoxon
Xidorn Quan
Ryan VanderMeulen
Olli Pettay
Ehsan Akhgari
Timothy Nikkel
Mark Striemer
Andrew McCreight
Manish Goregaokar
Oriol
Jim Blandy
Nathan Froyd
Lee Salzman
Honza Bambas
Ben Hearsum
Eitan Isaacson
Nicolas B. Pierron
Bill McCloskey