W3C home > Mailing lists > Public > public-html@w3.org > March 2010

Re: document.load: History and a proposal

From: Adam Barth <w3c@adambarth.com>
Date: Sat, 27 Mar 2010 15:06:49 -0700
Message-ID: <5c4444771003271506r7b98a0d5kdc6bc2a0b133e82e@mail.gmail.com>
To: timeless <timeless@gmail.com>
Cc: HTML WG <public-html@w3.org>, Maciej Stachowiak <mjs@apple.com>, Smaug <Olli.Pettay@gmail.com>
On Sat, Mar 27, 2010 at 12:54 PM, timeless <timeless@gmail.com> wrote:
> On Sat, Mar 27, 2010 at 1:47 AM, Adam Barth <w3c@adambarth.com> wrote:
>> The document.load appears to have been implemented originally in
>> Internet Explorer.  Netscape implemented the API in 2000 on all
>> documents.  In 2001, Netscape discovered that exposing the load API on
>> all documents creates compatibility problems with some seemingly
>> innocuous JavaScript:
>
>> 1) Abandon document.load.  In 2009, timeless proposed deprecating
>> document.load (see
>> <https://bugzilla.mozilla.org/show_bug.cgi?id=494705>).  We could
>> ignore the API and hope the web will eventually stop using it.  I do
>> not favor this approach given the number of bugs filed against
>> WebKit-based browsers for not implementing the API and my personal
>> experience with such web sites.
>
> sadly i don't have very good filters for my own work, since it's been
> brought up again, i can easily push this through after I return home
> from my current trip.

I'm not sure "pushing it through" is the best course of action.  That
just means Firefox will have the same compatibility issues as WebKit,
and I wouldn't have been able to file a recent expense report.

>> I propose we adopt approach (2) because it has the highest assurance
>> of being compatible with the web.  However, some members of the WebKit
>> community oppose this approach because of the harm it would cause to
>> HTML5's unification of the Document-like interfaces.
Received on Saturday, 27 March 2010 22:07:55 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:00 UTC