As per the following change to the spec:
6b3d7240b5
The additional failure annotation is added because we don't currently treat
text-combine-upright as non-animatable and this patch exposes the existing bug
(bug 1654195).
Differential Revision: https://phabricator.services.mozilla.com/D84308
This fixes performance issues when there's a massive number of rules and
a massive DOM.
Instead of going through all rules for all the DOM, we now look stuff in
hashmaps.
Differential Revision: https://phabricator.services.mozilla.com/D83506
Instead add a pseudo-class that does the expected size="" attribute parsing.
Removing the Gtk-specific rule setting the text color since it doesn't
seem to have any effect currently.
Differential Revision: https://phabricator.services.mozilla.com/D83448
Forgot to follow up on these two remaining non-standard values that may have
been being used to reset a <meter> or <input type=number> back to its
original appearance, but which telemetry showed no usage of.
Differential Revision: https://phabricator.services.mozilla.com/D83598
Uses of `-moz-appearance: none` are changed to `appearance: none`.
Uses of other values that are simply reverting the appearance back to
its default are changed to `appearance: auto`.
Uses of values in UA sheets that are defining the inherent appearance of
widgets are changed to:
appearance: auto;
-moz-default-appearance: <value>;
since those values are either no longer supported on (-moz-)appearance,
or are still supported but only in some limited form.
There are some uses of `-moz-appearance: textfield` on <input
type=number> elements that are renamed to `appearance: textfield`.
Differential Revision: https://phabricator.services.mozilla.com/D83430
This hooks the "monochrome" media query and co to the
nsIPrintSettings.printInColor setting.
This print setting we're using is not exposed in the print preview UI,
but you can test it setting the print.print_in_color preference to
"false", and then print preview will correctly show up greyscale'd.
Once this lands, the UI folks just have to use it as they see fit :)
I would've liked to add a proper rendering test, but the print reftests
check only whether the PDF text matches.
I could add a test to printpreview_helper.xhtml, but I'm refactoring
that file in bug 1648064 so I'd rather wait a bit and add it in a
separate bug. The test for the media feature should make sure that we
test that code path at least.
Differential Revision: https://phabricator.services.mozilla.com/D83552
By the time we get to iterate over the longhands of a shorthand, we've
already advanced the range iterator, so we look at the next duration and
such, which causes this bug.
I'm seriously baffled that no existing test caught this when it
landed, neither in our internal test suite nor wpt... :/
Differential Revision: https://phabricator.services.mozilla.com/D82396
This avoids arbitrary precision loss when computing REM units and so on,
which is particularly important if we ever change the base of our app
units (but useful regardless).
Differential Revision: https://phabricator.services.mozilla.com/D79928
Add Gstreamer plugins to Arch Linux deps script
<!-- Please describe your changes on the following line: -->
I was unable to compile servo on my machine because of errors related to gst. Installing the following solved the issue.
---
<!-- 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
- [X] These changes do not require tests because only README is affected
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
This does not (yet) upgrade ./rust-toolchain
The warnings:
* dead_code "field is never read"
* redundant_semicolons "unnecessary trailing semicolon"
* non_fmt_panic "panic message is not a string literal, this is no longer accepted in Rust 2021"
* unstable_name_collisions "a method with this name may be added to the standard library in the future"
* legacy_derive_helpers "derive helper attribute is used before it is introduced" https://github.com/rust-lang/rust/issues/79202
Bump futures from 0.1.30 to 0.1.31
Bumps [futures](https://github.com/rust-lang-nursery/futures-rs) from 0.1.30 to 0.1.31.
<details>
<summary>Commits</summary>
<ul>
<li><a href="49ad690a60"><code>49ad690</code></a> Release 0.1.31 (<a href="https://github-redirect.dependabot.com/rust-lang-nursery/futures-rs/issues/2359">#2359</a>)</li>
<li><a href="8b26bd830e"><code>8b26bd8</code></a> Migrate CI to GitHub Actions (<a href="https://github-redirect.dependabot.com/rust-lang-nursery/futures-rs/issues/2360">#2360</a>)</li>
<li><a href="cfe1d82c15"><code>cfe1d82</code></a> Backport to 0.1: FuturesUnordered: Do not poll the same future twice per iter...</li>
<li>See full diff in <a href="https://github.com/rust-lang-nursery/futures-rs/compare/0.1.30...0.1.31">compare view</a></li>
</ul>
</details>
<br />
[](https://dependabot.com/compatibility-score/?dependency-name=futures&package-manager=cargo&previous-version=0.1.30&new-version=0.1.31)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
</details>
Bump num-traits from 0.2.12 to 0.2.14
Bumps [num-traits](https://github.com/rust-num/num-traits) from 0.2.12 to 0.2.14.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/rust-num/num-traits/blob/master/RELEASES.md">num-traits's changelog</a>.</em></p>
<blockquote>
<h1>Release 0.2.14 (2020-10-29)</h1>
<ul>
<li>Clarify the license specification as "MIT OR Apache-2.0".</li>
</ul>
<p><strong>Contributors</strong>: <a href="https://github.com/cuviper">@cuviper</a></p>
<h1>Release 0.2.13 (2020-10-29)</h1>
<ul>
<li><a href="https://github-redirect.dependabot.com/rust-num/num-traits/pull/180">The new <code>OverflowingAdd</code>, <code>OverflowingSub</code>, and <code>OverflowingMul</code> traits</a>
return a tuple with the operation result and a <code>bool</code> indicating overflow.</li>
<li><a href="https://github-redirect.dependabot.com/rust-num/num-traits/pull/185">The "i128" feature now overrides compiler probes for that support</a>.
This may fix scenarios where <code>autocfg</code> probing doesn't work properly.</li>
<li><a href="https://github-redirect.dependabot.com/rust-num/num-traits/pull/186">Casts from large <code>f64</code> values to <code>f32</code> now saturate to infinity</a>. They
previously returned <code>None</code> because that was once thought to be undefined
behavior, but <a href="https://github-redirect.dependabot.com/rust-lang/rust/issues/15536">rust#15536</a> resolved that such casts are fine.</li>
<li><a href="https://github-redirect.dependabot.com/rust-num/num-traits/issues/192"><code>Num::from_str_radix</code> documents requirements for radix support</a>, which
are now more relaxed than previously implied. It is suggested to accept at
least <code>2..=36</code> without panicking, but <code>Err</code> may be returned otherwise.</li>
</ul>
<p><strong>Contributors</strong>: <a href="https://github.com/cuviper">@cuviper</a>, <a href="https://github.com/Enet4">@Enet4</a>, <a href="https://github.com/KaczuH">@KaczuH</a>, <a href="https://github.com/martin-t">@martin-t</a>, <a href="https://github.com/newpavlov">@newpavlov</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="e8da6fe581"><code>e8da6fe</code></a> Release 0.2.14</li>
<li><a href="deedb93eb8"><code>deedb93</code></a> Merge <a href="https://github-redirect.dependabot.com/rust-num/num-traits/issues/193">#193</a></li>
<li><a href="5e3352c2e4"><code>5e3352c</code></a> Update the names for overflowing results</li>
<li><a href="5b6299204a"><code>5b62992</code></a> Document relaxed requirements for Num::from_str_radix</li>
<li><a href="37e765824d"><code>37e7658</code></a> Release 0.2.13</li>
<li><a href="f0a980b29e"><code>f0a980b</code></a> Merge <a href="https://github-redirect.dependabot.com/rust-num/num-traits/issues/185">#185</a> <a href="https://github-redirect.dependabot.com/rust-num/num-traits/issues/186">#186</a> <a href="https://github-redirect.dependabot.com/rust-num/num-traits/issues/190">#190</a></li>
<li><a href="26c9ad2256"><code>26c9ad2</code></a> Merge <a href="https://github-redirect.dependabot.com/rust-num/num-traits/issues/180">#180</a></li>
<li><a href="a939c51793"><code>a939c51</code></a> Correct docs for overflowing docs</li>
<li><a href="6c499ada16"><code>6c499ad</code></a> Normalize the comment style</li>
<li><a href="234e855576"><code>234e855</code></a> Allow large f64-to-f32 to saturate to infinity</li>
<li>Additional commits viewable in <a href="https://github.com/rust-num/num-traits/compare/num-traits-0.2.12...num-traits-0.2.14">compare view</a></li>
</ul>
</details>
<br />
[](https://dependabot.com/compatibility-score/?dependency-name=num-traits&package-manager=cargo&previous-version=0.2.12&new-version=0.2.14)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
</details>
