They have been disabled since bug 1688695. There's a variety of
table-caption bugs that would be easier to fix if we didn't have to
account for side-captions.
Differential Revision: https://phabricator.services.mozilla.com/D165690
For things that can be parsed as Javascript, we need to figure out
if they are JSON, and we want to block opaque JSON resources for ORB.
This initial version just checks the first byte of the response, and
blocks it if it's a curly bracket.
Differential Revision: https://phabricator.services.mozilla.com/D163283
They have been disabled since bug 1688695. There's a variety of
table-caption bugs that would be easier to fix if we didn't have to
account for side-captions.
Differential Revision: https://phabricator.services.mozilla.com/D165690
They have been disabled since bug 1688695. There's a variety of
table-caption bugs that would be easier to fix if we didn't have to
account for side-captions.
Differential Revision: https://phabricator.services.mozilla.com/D165690
Some X servers move focus along with the mouse. They do not do that if
the pointer is grabbed tho.
Since we want to rollup popups on focus-out events, and not grabbing the
pointer causes the main window to lose focus, let's try to grab the
pointer again.
This reintroduces similar code to the one removed in bug 1798131, but
with a couple critical differences:
* It's simpler.
* We use less-deprecated APIs, though we can't use GdkSeat because we
still support Gtk < 3.20 in theory.
* We don't capture enter/leave-notify events in the grab mask. This
doesn't seem to be needed, and prevents the spurious
enter/leave-notify events that caused me to remove the pointer grabs
to begin with.
I tweaked test_panel_mouse_coords.xhtml so that the pointer ends up
inside the panel input region, otherwise the motion event goes to the
actual window and the test fails. It's kind of a bug that we dispatch
mousemove events for that region anyways, but...
Add a pref for this behavior, and some related logging, since it may
make it easier to debug stuff in the future, and there are some WMs that
don't support querying their name.
Differential Revision: https://phabricator.services.mozilla.com/D165735
The spec is still using `Scroll-linked`, so we exclude the change of WPT tests.
I believe WPT will get updates once the spec doc is renamed.
Differential Revision: https://phabricator.services.mozilla.com/D165914
Some X servers move focus along with the mouse. They do not do that if
the pointer is grabbed tho.
Since we want to rollup popups on focus-out events, and not grabbing the
pointer causes the main window to lose focus, let's try to grab the
pointer again.
This reintroduces similar code to the one removed in bug 1798131, but
with a couple critical differences:
* It's simpler.
* We use less-deprecated APIs, though we can't use GdkSeat because we
still support Gtk < 3.20 in theory.
* We don't capture enter/leave-notify events in the grab mask. This
doesn't seem to be needed, and prevents the spurious
enter/leave-notify events that caused me to remove the pointer grabs
to begin with.
For now I reintroduced the grab on X11 whole-sale.
If we see back the intermittent failures from bug 1607713 we might want
to detect the environment in a more fine-grained fashion as suggested on
the code comment.
I tweaked test_panel_mouse_coords.xhtml so that the pointer ends up
inside the panel input region, otherwise the motion event goes to the
actual window and the test fails. It's kind of a bug that we dispatch
mousemove events for that region anyways, but...
Also, add a pref for this behavior, and some related logging, since it
may make it easier to debug stuff in the future.
Differential Revision: https://phabricator.services.mozilla.com/D165735
For things that can be parsed as Javascript, we need to figure out
if they are JSON, and we want to block opaque JSON resources for ORB.
This initial version just checks the first byte of the response, and
blocks it if it's a curly bracket.
Differential Revision: https://phabricator.services.mozilla.com/D163283
Since Bug 1753373 fix, a regression is not reported yet. Then it seems OK to enable video overlay of software decoded video until early beta on Windows.
Differential Revision: https://phabricator.services.mozilla.com/D165512
This changes about:neterror to show a specific error page when the DNS failure
occurs for a TRR mode3 page load. This offers the user more information about
the failure, and some options.
This page will be further improved at a later stage when we add a better
DNS over HTTPS settings page.
The page is visible when the browser is using DNS over HTTPS without fallback
to native DNS. To achieve this the user sets `network.trr.mode` to `3` then
loads a page such as `http://nonexistant.test`.
If a top level load's channel returns NS_ERROR_UNKNOWN_HOST we look at
whether the page was indeed loaded with an effectiveTRRMode == TRRONLY
(some loads are excluded from using TRR).
When that is true, we present the error page allowing the user to retry,
exclude the domain from TRR, or open the settings page.
Note: This initial implementation will not work if the
`network.dns.disablePrefetch` pref is set to true. In that case nsHttpChannel
does not get an OnLookupComplete callback, so it doesn't have the
effectiveTRRMode and trrSkipReason. This will be fixed in bug 1805372.
Project plan: https://docs.google.com/document/d/12IGABt1eXI276qHduXXbVZqRFrhLN7Ad3gKEgxz81sE
Copy deck: https://docs.google.com/document/d/130UTox8bQbybjYIwvltR4qBg2hWjsGhuNUHypLwUAEQ
Depends on D164642
Differential Revision: https://phabricator.services.mozilla.com/D164347