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

Re: document.load: History and a proposal

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 27 Jul 2010 17:51:50 +0200
Message-ID: <AANLkTimsNhDk-b3yBQx4qKqZ2GFQKU4i91-8a4yWAF5y@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Ian Hickson <ian@hixie.ch>, HTML WG <public-html@w3.org>
On Tue, Jul 27, 2010 at 5:47 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> On Mon, Jul 26, 2010 at 10:36 PM, Ian Hickson <ian@hixie.ch> wrote:
>> On Sat, 27 Mar 2010, Maciej Stachowiak wrote:
>>> I'm much more concerned about the synchronous version of this API. Is
>>> there a way to tell how many sites use specifically the synchronous
>>> pattern, and how many depend on the request being fulfilled
>>> synchronously? It's true that synchronous XHR already allows blocking
>>> network I/O, but it's a regrettable part of the platform and I'd rather
>>> not add more constructs along these lines.
>> I haven't avoided the sync API here, but I'd be glad to remove it if
>> browser vendors are not going to support it / are going to remove support.
>> As written, the spec can have the sync aspects easily removed.
> Does webkit not support synchronous document.load already? If not, I'd
> be happy to attempt to remove it from firefox and see what shakes out.
> I'd also love to remove document.load entirely, but I'm less confident
> that is doable. Does anyone have data? At the very least I'd like to
> restrict document.load to not work on displayed documents, i.e.
> documents with a defaultView != null.

WebKit doesn't have document.load at all.  This is one of WebKit's
biggest compat problems.  I don't know whether the compat issues are
coming from the sync or async versions.

Received on Tuesday, 27 July 2010 15:52:47 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:21 UTC