W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Fakepath revisited

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Thu, 3 Sep 2009 16:14:31 -0400
Message-ID: <7c2a12e20909031314u53d56699paed9725c94332f6e@mail.gmail.com>
On Thu, Sep 3, 2009 at 1:05 PM, Alex Henrie<alexhenrie24 at gmail.com> wrote:
> If the cost of changing the browsers is equal

Is it?  What do the implementors on each side think?  Just because the
same number of lines would have to be changed doesn't mean the cost is
equal, in terms of getting people to agree if nothing else.

On Thu, Sep 3, 2009 at 1:24 PM, Eduard Pascual<herenvardo at gmail.com> wrote:
> Currently, all major browsers implement "non-standard behaviour for
> compatibility with existing content", quoting your own words, or
> "quirks modes", to use more common terms.

Well, with the advent of HTML 5, it's now *standard* behavior for
compatibility with existing content.  :)  The overwhelming majority of
compat stuff works in "standards mode" too, though, not just quirks

> Does the HTML5 spec define
> what should trigger each "quirks mode" and how browsers should behave
> when in those modes?

Yes.  I don't know if the pages relying on fakepath would trigger
quirks mode, though.
Received on Thursday, 3 September 2009 13:14:31 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC