Ugh. This does seem like the right thing to do in a bad situation. Thanks
and thanks to Anne for working to get the spec updated.
-Ekr
On Wed, Aug 19, 2020 at 10:10 AM Gijs Kruitbosch
wrote:
> It's been pointed out to me that I neglected to merge the "intent to
> prototype" requirements into
It's been pointed out to me that I neglected to merge the "intent to
prototype" requirements into my email. So:
Platform coverage: everywhere.
Preference: no pref.
DevTools bug: covered by existing network tooling (it already shows the
full header).
Other browsers: as noted, they already do
As of Firefox 81 I intend to update our parsing of Content-Disposition
headers so that spaces/tabs in unquoted values are treated as part of
the value (rather than as a separator, cutting off the value).
This is what Blink and Webkit already do.
Bug for this change:
Hi all,
With Firefox 80 release candidates already shipping, we are nearing the
end of the Nightly 81 cycle.
In order to avoid invalidating the testing we get out of late Nightly
and to ensure that we can roll out 81 Betas to a wider audience with
confidence, we'd like to ask that any risky
`Document.execCommand()` may cause firing DOM events and/or running some
observers. Therefore, web apps can call it recursively. However,
Chromium has already stopped supporting it (since 2014)[1][2].
And it'll be documented in execCommand spec[3].
This is testing in Nightly and early
5 matches
Mail list logo
