On Thu, Sep 5, 2013 at 7:32 PM, Mike Hoye <mh...@mozilla.com> wrote: > On 2013-09-05 10:10 AM, Henri Sivonen wrote: >> >> It's worth noting that for other classes of authoring errors (except for >> errors in https deployment) we don't give the user the tools to remedy >> authoring errors. > > Firefox silently remedies all kinds authoring errors.
Silently, yes. I was trying to ask about surfacing error-remedying UI to the user. We do surface such UI for https deployment errors inspiring academic papers about how bad it is that users are exposed to such UI. On Thu, Sep 5, 2013 at 9:29 PM, Robert Kaiser <ka...@kairo.at> wrote: > UTF-8 is what is being suggested > everywhere as the encoding to go with, and as we should be able to detect it > easily enough, we should do it and switch to it when we find it. Considering what Aryeh said earlier in this thread, do you have a suggestion how to do that so that 1) Incremental parsing and rendering aren't hindered. AND 2) The results are deterministic and reliable and don't depend on the byte position of the first non-ASCII byte in the data stream. AND 3) The processing of referenced unlabeled CSS and JavaScript doesn't have race conditions even with speculative parsing involved, is unsurprising and doesn't break legacy content. AND 4) We don't incur the performance penalty of re-parsing or re-building the DOM if authors start labeling UTF-8 less due to no longer having to label. AND 5) Side effects of scripts are not effected twice if authors start labeling UTF-8 less due to no longer having to label. ? On Thu, Sep 5, 2013 at 6:15 PM, Adam Roach <a...@mozilla.com> wrote: > As to the "why," it comes down to balancing the need to let the publisher > know that they've done something wrong against punishing the user for the > publisher's sins. Two problems: 1) The complexity of the platform increases in order to address a fringe case. 2) Making publishers' misdeeds less severe in the short term makes it more OK for publishers to engage in the misdeeds, which in the light of #1 leads to long-term problems. (Consider the character encoding situation in Japan and how HTML parsing in Japanese Firefox is worse than in other locales as the result.) -- Henri Sivonen hsivo...@hsivonen.fi http://hsivonen.iki.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
