On Tue, Apr 22, 2014 at 3:58 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > How reliable is our telemetry data here?
I suppose as reliably as telemetry data in general. I suppose its reliability is hard to measure. > I'm not really sure how the > measurement works. Is it based on the number of times that we encounter > this encoding per the number of pages loaded in a session? No. > Or is it a > boolean flag indicating whether we've hit the encoding in a given session? Yes. > Do we have any reason to believe that the portion of our users opting in to > Telemetry on the release channel correctly represents the potential > demographics who might be viewing pages written in these kinds of encodings? I have no reason to believe that telemetry wouldn't be representative of actual demand. > Also, what is the status of the support for these encodings in other UAs? Chrome doesn't support the encoding being removed here and Presto-Opera didn't support them, either. Non-support in Chrome and Presto-Opera is what made us dare to stop exposing these encodings to the Web earlier. IE and Safari support all kinds of cruft, including DOS encodings, as a matter of exposing underlying system libraries without regard to the actual needs of the Web. > I'm somewhat worried that we might break some Web pages for users who are > not fairly represented in our Telemetry data, and that we may not hear about > this before this change hits the release channel. We have already stopped exposing these encodings to the Web. We stopped recognizing the labels for these encodings in Firefox 19 for the purpose of Web content being able to request the use these encodings. However, we still kept around the possibility to manually choose these encodings from the menu as an override. We removed them from the menus in Firefox 28. At the time of Firefox 19, one person in Spain noticed that IBM850 (DOS Western European) went away. The affected page was a page maintained by this person himself. At the time of Firefox 28, one person noticed that IBM862 (DOS Hebrew) went away. These have been isolated cases of people who knowingly use legacy encodings noticing their own stuff breaking. At the time of Firefox 28, another person in Spain noticed that IBM850 went away. Unclear if that was a self-maintained case or not. DOS Hebrew has been even less interoperable than the other DOS encodings, because browsers didn't agree on whether it was a visual or logical encoding. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
