Due to the asynchronous nature of browsers the second
user prompt might not be opened immediately. As such
the test has to wait for the user prompt to appear.
Differential Revision: https://phabricator.services.mozilla.com/D105318
Fedora 19 and 20 were released in 2013. If these docs haven't been
adjusted for modern Fedora, they're probably out-of-date.
Differential Revision: https://phabricator.services.mozilla.com/D104733
When a user is at the top-level "Getting Set Up" page, they should be
shown which path to take (Windows/Mac/Linux) without redundantly showing
the platform-specific technicalities.
Differential Revision: https://phabricator.services.mozilla.com/D104099
* Puts the docs in order, so that contributors aren't jumping to the
middle of the page to install system tools, then back to the top to
clone Firefox.
* Removes docs on MacPorts since it's being removed in bug 1688263.
* Removes step to manually install brew packages since that happens
automatically in bootstrap now.
* Simplifies mercurial installation docs
* Removes unnecessary mozconfig-tweaking instructions
* Removes almost-always-unnecessary DEFINE and troubleshooting
information.
Differential Revision: https://phabricator.services.mozilla.com/D102974
* Puts the docs in order, so that contributors aren't jumping to the
middle of the page to install system tools, then back to the top to
clone Firefox.
* Removes docs on MacPorts since it's being removed in bug 1688263.
* Removes step to manually install brew packages since that happens
automatically in bootstrap now.
* Simplifies mercurial installation docs
* Removes unnecessary mozconfig-tweaking instructions
* Removes almost-always-unnecessary DEFINE and troubleshooting
information.
Differential Revision: https://phabricator.services.mozilla.com/D102973
We use `pip@20.3.1`, but our currently-vendored
`pip-tools@5.3.1` only supports up to
`pip 20.1.1`.
Looks like a new version of `pip-tools` has changed the formatting
of `requirements.txt`, so I apologize for the more-complicated-than
-necessary diff.
Differential Revision: https://phabricator.services.mozilla.com/D104859
I originally added the operandTruncateKind check in canTruncate because MMod and MDiv will always force bailouts for their operands. This runs into problems, because some other implementations of operandTruncateKind rely on state that is not set until later. (Some ops call `truncateKind()`, which is set by the `needsTruncation()` implementation for that op. MCompare uses `truncateOperands_`, which is set by `MCompare::truncate`.
After several attempts, I think the simplest option is to check specifically for MDiv and MMod in `canTruncate`. These are the only two instructions that can return `TruncateAfterBailouts` from `operandTruncateKind` without using `TruncateAfterBailouts` themselves.
I've also reduced the fuzz test somewhat.
Differential Revision: https://phabricator.services.mozilla.com/D105059
Note that quite a few Mali-Txxx devices still won't get webrender, due
to lack of GL_OES_EGL_image_external_essl3 support. Bug 1507074 tracks
lifting this requirement.
Depends on D105338
Differential Revision: https://phabricator.services.mozilla.com/D105339
Webrender has been enabled for most Adreno 5xx and 6xx devices for a
while now, but 505 and 506 were held back due to bug 1609191. We were
seeing a moderate number of crashes during what we suspected was
shader compilation.
The crashes on 505 and 506 have all but disappeared. Additionally,
after shipping to the wider release audience we saw the same crashes
on other 5xx devices, not just 505 and 506, but the numbers were never
so high as to be worrying. So we are safe to ship to 505 and 506 as
well.
Depends on D105337
Differential Revision: https://phabricator.services.mozilla.com/D105338
This test highlights the issue reported in Bug 1673829, where the location links
in the rule view are incorrect after navigating, when `devtools.testing.enableServerWatcherSupport`
is true.
At the moment, this test fails when we try to enable the stylesheet resource
watcher support (Bug 1685268).
Differential Revision: https://phabricator.services.mozilla.com/D105286
This enables us to get a wheel for python cryptography instead of
building it ourselves, which breaks because we don't have a rust
compiler.
Differential Revision: https://phabricator.services.mozilla.com/D105060
AutoTArray gives us some memory overhead and the benefits it provides
might not be that useful since PerformanceEventTiming only works
for certain event types.
Differential Revision: https://phabricator.services.mozilla.com/D105078
Previously we had encountered issues when rendering partial regions of
picture cache tiles on Mali-Gxx devices. These often manifested as
patterns of black squares and rectangles. We worked around this by
ensuring that we always clear and render the entire tile. We have now
had a report of a similar looking problem on a Mali-Txxx devices, so
apply the same workaround there.
Differential Revision: https://phabricator.services.mozilla.com/D105278
We should not assume that any target class is always top level.
Instead the `isTopLevelTarget` option should be explicitly passed whenever relevant.
Differential Revision: https://phabricator.services.mozilla.com/D105270
This brings the time down to 1.6ms from 4.8ms on the test-case in the
bug. This should be improvable too, but I think this is a nice
improvement for regular styling as well.
Differential Revision: https://phabricator.services.mozilla.com/D105187