On Mon, Dec 2, 2019 at 2:42 PM Henri Sivonen wrote:
> 1. On _unlabeled_ text/html and text/plain pages, autodetect _legacy_
> encoding, excluding UTF-8, for non-file: URLs and autodetect the
> encoding, including UTF-8, for file: URLs.
>
> Elevator pitch: Chrome already did this unilaterally. The
On 12/9/19 6:24 AM, Henri Sivonen wrote:
Good point. I'll use tentative WPTs for end-to-end automated tests.
Thank you!
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On Thu, Dec 5, 2019 at 8:08 PM Boris Zbarsky wrote:
>
> On 12/2/19 7:42 AM, Henri Sivonen wrote:
> > Since there isn't a spec and Safari doesn't implement the feature,
> > there are no cross-vendor tests.
>
> Could .tentative tests be created here, on the off chance that we do
> create a spec for
On 12/2/19 7:42 AM, Henri Sivonen wrote:
Since there isn't a spec and Safari doesn't implement the feature,
there are no cross-vendor tests.
Could .tentative tests be created here, on the off chance that we do
create a spec for this at some point?
-Boris
# Summary
The template says this section should state the benefit to Web
developers. There is intentionally no benefit to Web developers. This
pair of features is meant to benefit users who encounter
badly-authored legacy pages, so that Firefox can retain users instead
of the users trying in
5 matches
Mail list logo
