Intent to ship: Enable pointer events on disabled form elements

[Kagami Rosylight]

As of 2024-01-26 I intend to turn `dom.forms.always_allow_pointer_events.enabled` on by default on all platforms. This pref allows firing pointer events on disabled form elements e.g. <button> and <input>.

This has been in discussion in https://github.com/whatwg/html/issues/2368 and https://github.com/whatwg/html/issues/5886, and both Chrome and Safari are now shipping the behavior in a good consensus.

Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1653882

Standard: We still need to adjust the HTML spec to reflect the consensus. The updated behavior is already covered on WPT: https://wpt.fyi/results/html/semantics/disabled-elements

[Randell Jesup]

I just landed support for zstd Accept-Encoding support on all platforms in Firefox 126.  This will allow servers to send Firefox zstandard-compressed streams.

Currently Facebook and associated properties (Instagram, etc) use zstd encoding extensively, and other sites use it as well when the browser supports it.

We only enable zstd for secure connections to avoid the CRIME and BREACH attacks on compressed data, for the same reasons brotli is only used on secure connections.

Chrome just enabled zstd support in 123 (a short time ago).

Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1871963

Standard: https://datatracker.ietf.org/doc/html/rfc8878

Platform coverage: all

Preference: adds zstd to network.http.accept-encoding.secure.  It can be disabled by removing this

Other Browsers:

- Blink: Shipped in 123

Safari: https://github.com/WebKit/standards-positions/issues/168

--

Randell Jesup, Mozilla