On 2014-04-22, 9:24 AM, Henri Sivonen wrote:
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
On 4/22/2014 7:09 AM, Henri Sivonen wrote:
Thunderbird developers will be able to import the code into
comm-central and continued to support these encodings for email and
NNTP if they so choose.
Based on my charset explorations in NNTP, the only common IBM* encoding
not present on the encoding
On Tue, Apr 22, 2014 at 3:58 PM, Ehsan Akhgari 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 encoun
On Tue, Apr 22, 2014 at 2:58 PM, Ehsan Akhgari wrote:
> How reliable is our telemetry data here? 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? Or is it a
> boolean flag indicatin
On 2014-04-22, 8:09 AM, Henri Sivonen wrote:
We already do not expose MS-DOS encodings other than Cyrillic to the
Web. We still expose them to Firefox extensions in some APIs.
Telemetry shows that usage varies from non-existent to extremely rare
(28 sessions out of 180.82 million sessions for the
We already do not expose MS-DOS encodings other than Cyrillic to the
Web. We still expose them to Firefox extensions in some APIs.
Telemetry shows that usage varies from non-existent to extremely rare
(28 sessions out of 180.82 million sessions for the Western European
DOS code page).
In order to
6 matches
Mail list logo
