This will better highlight what is closing. Not the DevToolsClient, but just the transport class.

Differential Revision: https://phabricator.services.mozilla.com/D108812

Differential Revision: https://phabricator.services.mozilla.com/D108797

Differential Revision: https://phabricator.services.mozilla.com/D110640

Bug 1704092 - Disable chrome/chromium tests on mac 10.15 for perma-failures. r=perftest-reviewers,Bebe

Differential Revision: https://phabricator.services.mozilla.com/D111414

Bug 1704474 - Remove pin/unpin page action context menu items. r=adw,fluent-reviewers,extension-reviewers,flod,zombie

The bug calls for these items to be hidden with JS, but they were going to be removed anyways post-Proton. The removal of some subtests in browser/base/content/test/pageActions tests is consistent with [this comment](https://searchfox.org/mozilla-central/rev/d9f6cded535d202a9ade4a530e653e659bcb5bbd/browser/base/content/test/pageActions/browser.ini#7), which says that were are removing that test coverage post-Proton anyways.

Differential Revision: https://phabricator.services.mozilla.com/D111713

Differential Revision: https://phabricator.services.mozilla.com/D111525

This patch tries to address the issue that legacy CJK extensions have various
extended variants where the core of the encoding is compatible but the edges
are incompatible. Without this patch, we reject e.g. Big5 if it has a single
character from the UAO extension or a single Windows end-user-defined character.

Likewise for the other legacy CJK encodings.

This patch tolerates:

* All Big5 extensions (the motivating part of this patch).
* Windows EUDC for EUC-KR.
* Classic Mac OS extensions to Shift_JIS, EUC-KR, GBK, and Big5 to the
  extent practical considering conflicting definitions of what constitutes
  a lead byte in the Encoding Standard but a single-byte extension in
  Classic Mac OS.
* JIS X 0213 / 2004 extensions to Shift_JIS and EUC-JP. (It's unclear if
  these have actual deployment.)

Tolerating means that the occurrence of an extension character doesn't
disqualify a candidate but only applies a penalty to the pending score.
If there is enough other convincing content, it should be able to overcome
the penalty.

Differential Revision: https://phabricator.services.mozilla.com/D111372

Bug 1697769 - Apply implicit pointer capture only for pointer events that are generated from the touch events; r=smaug

Pointer capture would override the capturing content set in PresShell for mouse
event, it isn't affect touch event because dispatching touch event would take
the capturing content in PresShell into account, i.e.
https://searchfox.org/mozilla-central/rev/fa48ebee58d59fa846919c3e2c3122b08db57c9c/layout/base/PresShell.cpp#8712-8719

Touch input isn't always generating a touch event, but a compabitility mouse
event with the touch as inputsource, e.g. chrome popup window on Windows platform,
see https://searchfox.org/mozilla-central/rev/3de2db87f3c9001ae478318d47a2ca3427574382/widget/windows/nsWindow.cpp#8130-8134
In such case, we don't apply implicit pointer capture to prevent the capturing
content set in PresShell being overried which could cause the drag to scroll
doesn't work.

Differential Revision: https://phabricator.services.mozilla.com/D111085

Differential Revision: https://phabricator.services.mozilla.com/D111525

Differential Revision: https://phabricator.services.mozilla.com/D111059

Server-Timing was only being parsed with HTTPS. But this is overly
restrictive to developers, so it's better to restrict it to
secure origins which includes `http://localhost/`

Differential Revision: https://phabricator.services.mozilla.com/D111795

Differential Revision: https://phabricator.services.mozilla.com/D111608

Differential Revision: https://phabricator.services.mozilla.com/D111792

Safari does this. This reduces the runtime in the example linked from
comment 0 quite a lot (40ms on a local opt build, from ~130ms on a
release nightly build).

I added a pref because there's a slight chance of performance
regressions on pages that do not use attribute selectors, as we're now
doing more unconditional work per element (adding the attributes to the
bloom filter). But the trade-off should be worth it, I think.

Differential Revision: https://phabricator.services.mozilla.com/D111689

I need to use these from Rust to insert mapped attribute names in the
bloom filter, and this would save me handrolling even more bindings :)

Differential Revision: https://phabricator.services.mozilla.com/D111731

Backed out changeset ba593c7436f6 (bug 1689730) for failures on test_http_server_timing.js. CLOSED TREE

Differential Revision: https://phabricator.services.mozilla.com/D111586

Bug 1702467. Double tap zoom can make us zoom to a part of an element when we could fit the entire element at the same zoom. r=botond

If we double tap on an element that is narrower than the viewport at maximum we can get into a situation where we zoom on part (say the bottom half) of that element but we could easily fit the entire element.

This happens because the code that calculate the rect to zoom to (CalculateRectToZoomTo) doesn't know about the maximum zoom. So it proceeds as though we will fit the width of the element. Under that assumption we will have to cut off part of the element vertically, so the code centers the rect on the users tap point.

This ends up cutting off part of the element vertically when it is clear that the whole element can fit on screen, which is a pretty ugly result.

This is not my favourite patch. This seemed to make the most sense. Another option I considered was passing the tap point through to AsyncPanZoomController::ZoomToRect but I think this approach came out better: the calculation all happens in one place at one time.

Differential Revision: https://phabricator.services.mozilla.com/D110538

Server-Timing was only being parsed with HTTPS. But this is overly
restrictive to developers, so it's better to restrict it to
secure origins which includes `http://localhost/`

Differential Revision: https://phabricator.services.mozilla.com/D111795

Bug 1702179 - nsIndexedToHTML generated views - focus ring for directories only shows the right margin r=Gijs

Differential Revision: https://phabricator.services.mozilla.com/D111536

Differential Revision: https://phabricator.services.mozilla.com/D69509

Differential Revision: https://phabricator.services.mozilla.com/D110471

Differential Revision: https://phabricator.services.mozilla.com/D110470

The username searching heuristic locates a username like or an email like field
by:
1. Checking if the input field's type is 'email'.
2. Checking if the input field's autocomplete attribute is 'username' or 'email'
3. Searching 'username' and 'email' keyword in:
   - The input field's "id", "name", "classname", and "placeholder" attributes.
   - The input field's associate label

If any of the above rule matches, we consider the field a username or an
email field depending on the keyword that matches.

When both a username-like and an email-like field are found in a form, select
the username-like field as the final username field. If no field is
found by the above heuristic, assume the first field before the first
password is the username (This is how it works before the patch).

Note. Right now, even with the new heuristic, we still only search fields
preecede the first password field like what we did before. This is because
from the sites I have tested (~250 sites), all the username fields
precede the first password field. If it turns out this is not true for
some sites, we can consider searching all the input fields in the form.

Differential Revision: https://phabricator.services.mozilla.com/D110469

Bug 1697630 - [marionette] Remove non-WebDriver spec compliant "rotatable" capability. r=marionette-reviewers,jdescottes

This capability is not part of the WebDriver specification
and might have used in the past for B2G to indicate that
a mobile device allows screen orientation changes. This is
no longer used.

Differential Revision: https://phabricator.services.mozilla.com/D111781

Previously, the filter used to select which batches a primitive
was added to was simply a rectangle in picture space. In future
it will include information about the z-slice a primitive is on.

To handle this, add a BatchFilter struct which we can expand in
future patches with more information. Also switch the PrimitiveVisibility
and DirtyRegion structs to use the new type.

Differential Revision: https://phabricator.services.mozilla.com/D111779

Surprised this didn't cause more issues tbh.

Differential Revision: https://phabricator.services.mozilla.com/D111237

Differential Revision: https://phabricator.services.mozilla.com/D111789

WASI lacks of support many memory stuff like mmap, memory protections and etc, but
it has malloc so we can use it instead. Also, here we are stubbing out all
uses of the missing WASI memory functionality.

Differential Revision: https://phabricator.services.mozilla.com/D110075

Differential Revision: https://phabricator.services.mozilla.com/D111378

Actually, we disable all mochitests in dom/events on GeckoView now.

We should run mochitests even if on GeckoView if it is passed.

Differential Revision: https://phabricator.services.mozilla.com/D111607

Bug 1704338. Use promiseApzFlushedRepaints instead of promiseOnlyApzControllerFlushed in doubleTapOn. r=botond

No reason to only wait for the controller, I think we want to wait for the full repaint. Seems to make things less intermittent, the test in bug 1702464 was already using this.

Differential Revision: https://phabricator.services.mozilla.com/D111554

Differential Revision: https://phabricator.services.mozilla.com/D111553

Bug 1704338. Merge helper_touchscreen_doubletap_zoom.html and helper_touchpad_doubletap_zoom.html. r=botond

The new format lets us use the same test file with a different arg to test both kinds.

Differential Revision: https://phabricator.services.mozilla.com/D111552

Bug 1704687 - Refactor visibility flags and how pass-through picture visibility is handled. r=gfx-reviewers,lsalzman

Move PrimitiveVisibility flags inside the Coarse / Detailed enums
which will be important once these enum fields also include info
about the z-slice that a primitive exists on in a picture cache.

Add a `PassThrough` variant of the enum for pictures that are
containers without a surface. These pictures don't have a z-slice
since they don't have bounds, so it's simpler to handle them this
way for now (although we aim to remove them completely in future).

This meant moving how we currently handle the 3d render context
container picture during batching. This part is still quite untidy
but we aim to refactor it further in future.

Differential Revision: https://phabricator.services.mozilla.com/D111769

WASI lacks of support many memory stuff like mmap, memory protections and etc, but
it has malloc so we can use it instead. Also, here we are stubbing out all
uses of the missing WASI memory functionality.

Differential Revision: https://phabricator.services.mozilla.com/D110075