Fennec team decides that Fennec will turn off ICU support on release build now. So we need to able be build Firefox without ENABLE_INTL_API (Bug 1343725).
Bug 1341994 uses mozIMozIntl interface, but it is only defined with ENABLE_INTL_API. So we shouldn't expose intlUtils if ICU is turned off.
MozReview-Commit-ID: EiQKiF4BRQv
--HG--
extra : rebase_source : 97f329da11094248a37edc543b5b541500a73d18
That also fixed bug 1303156, since handling better the device pixel ratio makes
also the lines crisp.
MozReview-Commit-ID: Iyl6YLFFp5b
--HG--
extra : rebase_source : eff92ab5dd2a389329e6a800f95f3b3a4be36db4
While we're here, don't re-recompute the default computed values, just grab them
from the device.
MozReview-Commit-ID: GqqnPLIwN2F
Signed-off-by: Emilio Cobos Álvarez <emilio@crisal.io>
This fixes the DOM node size regression introduced by a previous Rust update: https://github.com/servo/servo/issues/15704
<!-- Please describe your changes on the following line: -->
---
<!-- 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
- [ ] These changes fix #__ (github issue number if applicable).
<!-- Either: -->
- [ ] There are tests for these changes OR
- [ ] These changes do not require tests because _____
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
Source-Repo: https://github.com/servo/servo
Source-Revision: e102577fe498c8f0cee43ba80b21dc9430be1e2b
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 034771746b27e5a6c7e2e96948a366d26f92cd6b
This is on top of #15888. Only the second commit needs review.
We put the more recently used item last, so iterating then from left to right is
pointless.
Source-Repo: https://github.com/servo/servo
Source-Revision: 7fa4a94bb154449702e5ae9422c3008a5195c714
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : fbf4742c4186ad27bd4d5ccd3e2319a5b0748b55
Instead of just reporting the value of the pref, also make sure that about:support
incorporates the runtime check of whether or not a touch device was discovered
in the widget code. The code to do this already exists in TouchEvent::PrefEnabled,
so we can just reuse that.
MozReview-Commit-ID: DN7FSlsDwD1
--HG--
extra : rebase_source : efb3d66e1669f8f2b038888ef2b1c8bb83f1c710
Handle the translation of eRestyle_Subtree into
(RESTYLE_SELF | RESTYLE_DESCENDANTS) in the From impl, too.
Source-Repo: https://github.com/servo/servo
Source-Revision: 2f8cf6afc32a61d7eb5139ce4106201b7275c84d
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : 7cd7cf344485a77287b35825540c25e95746459d
When a highlighter was created for a node that has been removed, it can no longer be
hidden due to a check performed in the hide method of the basic auto-refresh class.
While it makes sense not to display a highlighter for an invalid node, hiding a
highlighter should always remain possible.
MozReview-Commit-ID: ChkmecJeqy9
--HG--
extra : rebase_source : 6dfbbdf78f7b59ab8264397f837fa61601bf72ee
The list of reftests modified here is based on searching for all reftest.list files with the "haveTestPlugin" string.
MozReview-Commit-ID: L0Pw6ZMwAF1
--HG--
extra : rebase_source : 85238d66a97d279f84c4eaba7f7cc5d6520eaef2
Note that this test currently is broken/disabled in e10s mode. That's covered by bug 1090576, but this patch doesn't make it worse because chrome mochitests run in local mode always anyway.
MozReview-Commit-ID: L4hJ8LkiSNG
--HG--
extra : rebase_source : 1e932cb1f96e8ef258c16363da558ea843b99462
The previous attempt at this didn't handle jobs that were keyed by platform,
which was most of them.
MozReview-Commit-ID: IC602td532T
--HG--
extra : rebase_source : 95cdf9ad37df8ef6665665f11e59f8ae8304dbd2
By always clearing any possible highlighters first, it helps handle the case of
toggling RDM, which does trigger `window-ready` even though the old highlighter
content is still live on the page.
MozReview-Commit-ID: FCRHW1AyiyB
--HG--
extra : rebase_source : 1a9a3d8bf1d3788ba260ccd837450c3a1c81bfe7