Most of this patch is updating a few places that use gfxMatrix to use
the equivalent-but-differently-named functions on MatrixDouble:
- Translate/Rotate/Scale get turned into PreTranslate/PreRotate/PreScale
- Transform(Point) gets turned into TransformPoint(Point)
- gfxMatrix::TransformBounds(gfxRect) gets turned into
gfxRect::TransformBoundsBy(gfxMatrix).
- gfxMatrix::Transform(gfxRect) gets turned into
gfxRect::TransformBy(gfxMatrix).
The last two functions are added in this patch as convenience wrappers
to gfxRect instead of Matrix.h because we don't want Matrix.h to "know"
about gfxRect (to avoid adding gecko dependencies on Moz2D). Once we
turn gfxRect into a typedef for RectDouble these will be eliminated
anyway.
MozReview-Commit-ID: BnOjHzmOSKn
--HG--
extra : rebase_source : cf1692d1f0d44a4b05d684a66678739181a426d5
To allow MatrixDouble to be a drop-in replacement for gfxMatrix, it
needs to accept the "double" versions of Point, Rect, and Size. This
patch does that by adding some extra typedefs inside BaseMatrix to
abstract over that.
It also moves some function implementations into the .h file as they
don't need specialization. I left some function implementations in
the Matrix.cpp file:
- Rotation, because it is specialized for Float and Double, since it uses
sinf/cosf vs sin/cos in the two implementations.
- The Matrix4x4 multiplication operator overload, because if I put it
inside the BaseMatrix class declaration Matrix4x4 isn't defined yet
and the compiler doesn't like it.
MozReview-Commit-ID: K56dZjJhXWS
--HG--
extra : rebase_source : d009151942811a725ee6bf854238073e59665d5c
This extracts a BaseMatrix template of which Matrix is now a particular
specialization. The BaseMatrix allows us to reuse the same code for
floats and doubles, much like the other "base" classes (BasePoint,
BaseRect, etc.).
MozReview-Commit-ID: HO7bA83S9E0
--HG--
extra : rebase_source : dcd84d9a978cdea00bb54eb11eefcca9c6635901
We'd like to use routes like:
index.gecko.v2.mozilla-central.latest.firefox.decision
to automatically find the latest parameters.yml file from a decision task. Unfortunately,
sometimes the latest decision task happens to be triggered by a cron job which uses a different
target_tasks method and therefore won't generate the expected tasks.
This patch *should* create a different index for these types of decision tasks, though I'm not
sure how I can test it before pushing.
MozReview-Commit-ID: 1993ISgb1Dn
--HG--
extra : rebase_source : f86fc60e823e02b922e5eec888620a28f4dc254c
This patch updates the OS that the Talos test suites use when they run on linux64-ccov to Ubuntu 16.04.
MozReview-Commit-ID: 4hx0jhTXv1C
--HG--
extra : rebase_source : b0b05378a158b74e23b4f330154541e00c305353
In Photon, TabCounter has a new design and implementation which handles itself
private mode visual refresh by calling `TabCounter#setPrivateMode(boolean)`.
So we shouldn't call setTabsCounterPrivateMode anymore in BrowserToolbarTabletBase.
MozReview-Commit-ID: LKu4OiTQyJV
--HG--
extra : rebase_source : c31216fcc50e2c8aeadbd03773968c90b5b2f585
… which is being removed in rust-lang/rust#43012
Source-Repo: https://github.com/servo/servo
Source-Revision: 5baea7b73223283b551cf378bb714491a2383c28
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : bf5a743b537b8b238e83e8c84c69ce98e15ec410
By not using the JSON format when sending the capabilities to the
frame script, the values cannot be correctly decoded. As result
the capabilities will be reset to their default values for the
listener, and can cause various failures.
MozReview-Commit-ID: KaryoJiyd30
--HG--
extra : rebase_source : 206e45755d3ea9b6cbf2f2022a9a364dcf22d78e
In ToolbarDisplayLayout we use color span for Title, Domain...etc.
In Photon-flavor we use use different color in priavte mode. In
Australis-flavor, normal-mode and private-mode refers to same color, so
user should not aware anything different.
MozReview-Commit-ID: 30cGivl9oOz
--HG--
extra : rebase_source : d30d2afabacb19f540763604d0286fedb909f4a0
In Australis flavor, it use same color then user should not aware of any
changes.
In Photon-flaor, its style use UrlBar.Button to avoid involving tint color list.
In current design, we should not tint color for some drawable such as
Lock.
MozReview-Commit-ID: PSuCbNPKR7
--HG--
extra : rebase_source : 088b7a4d78ffcb02267b24c06eb7a4e9e08b1ab1
* search icon
* qrcode
* mic
In Australia-flavor, it still use not-theme-able drawable, hence its
appearance won't change even in private mode. In Photon-flavor, these
icons should change its color base on normal/private mode.
MozReview-Commit-ID: EOsJuKqv70d
--HG--
extra : rebase_source : 51d20548bd11bc6a7aeeb9283781ee321a8c8041
For debugging purposes it would be useful to see which observer
notifications have been received and handled by the Marionette
component.
MozReview-Commit-ID: 1EucCEjOXhu
--HG--
extra : rebase_source : 09864144c4b92d1652aee6b62c72b29d692bd2ce
It is helpful to let the user know how Marionette get started. So
INFO log lines have to be added for the command line argument and
the environment variable.
This is especially helpful to get in case of missing observer
notifications, under which the server socket is not getting
created, and the client just hangs.
MozReview-Commit-ID: 4TEF33CDJKP
--HG--
extra : rebase_source : 3246fbcce4a3db2beddf82fa7b62ac482f37dcb1
Since we implement following properties animatable, append to test.
* -moz-border-bottom-colors
* -moz-border-left-colors
* -moz-border-right-colors
* -moz-border-top-colors
MozReview-Commit-ID: E3zWaDcRdtE
--HG--
extra : rebase_source : 27301a4bc354f14cf3f90e8c8271be6022d99721
In this patch, implements following properties:
* background-image
* border-image-source
* mask-image
MozReview-Commit-ID: 30RdO0fMNr8
--HG--
extra : rebase_source : d4490b4d64e22a3bc1f022c37edc20363f7c0269
In this patch, implements following properties:
* -moz-border-bottom-colors
* -moz-border-left-colors
* -moz-border-right-colors
* -moz-border-top-colors
To realize, we introduced a binding method Gecko_GetMozBorderColors.
MozReview-Commit-ID: JeseSyl8rMG
--HG--
extra : rebase_source : 118b6659a7be58f7b84e6024bfeea0a13dad66c0
<!-- Please describe your changes on the following line: -->
This PR fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1371115
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
<!-- Either: -->
- [X] There are tests for these changes. Add some tests into dom/animation/test/ of m-c in patch 14. Also, remove test fail annotation from meta in wpt as patch 15.
Source-Repo: https://github.com/servo/servo
Source-Revision: 42e551f60614da58f47fd29cb095cd72733e38b8
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 8acead695cf4f6294e4f84be90cca616a555a0e0
Currently, it's not been managed yet that whether an event is posted to at least one remote process. So, for managing the state, BaseEventFlags should have a new bool flag and WidgetEvent and BaseEventFlags should have helper methods for it.
Additionally, this fixes a bug of nsGUIEventIPC.h. In a lot of ParamTraits, static_cast<Foo> is used for using base class's ParamTraits. However, it causes creating temporary instance with copy constructor. Therefore, WidgetEvent::MarkAsPostedToRemoteProcess() call in ParamTraits<mozilla::WidgetEvent>::Write() didn't work as expected.
MozReview-Commit-ID: DdafsbVfrya
--HG--
extra : rebase_source : 94205f3a7b36455c3c9f607c35866be033e627c1
Currently, we have 2 bool flags (and optional 2 bool flags with related purpose) for managing propagation state between parent process and remote process. However, it's really complicated. Actually, setting these flags and referring the flags is usually follow explanation.
So, for making simpler, WidgetEvent and BaseEventFlags should have some utility methods for making them as self documented code.
This patch moves WidgetKeyboardEvent::mIsReserved to BaseEventFlags::mIsReservedByChrome. That allows us to manage the cross process event propagation state in same place.
MozReview-Commit-ID: IXEDQJ4GpAZ
--HG--
extra : rebase_source : 5b63ac4f1d15e40e8bfc88423e336de28caa8ab6
It's unused except in test code (nsTestEntityTable). The patch removes that
test code, which also removes testing for UnicodeToEntity conversion, but the
test code wasn't being run anyway so it's no great loss.
(UnicodeToEntity conversion is still used by
nsHTMLContentSerializer::AppendAndTranslateEntities().)
