- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Mon, 18 Oct 2010 02:18:46 -0700 (PDT)
- To: public html <public-html@w3.org>
Adam Barth wrote: > Decoupling the property from the attribute seems undesirable. I agree that it's a bit distasteful. However, so far, all attempts to work around this distasteful bit by introducing new API surface (including my now-withdrawn .ordered proposal, a couple of privately discussed options and your proposal) have introduced worse complications than the slightly ugliness the semi-decoupling the async DOM property from the content attribute would be. The only proposal so far that has avoided this distastefulness without introducing complications arising from new API surface has been the proposal to make async default to false and as a result to make IE and WebKit change their default behavior. But that proposal has two complications too: 1) From Tony Gentilcore's email it seems at least WebKit isn't particularly likely to change its defaults, so we wouldn't get to interop if IE and/or WebKit are unwilling to change the default behavior. 2) There'd be nothing to feature-sniff to detect if async=false means ordered execution. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Monday, 18 October 2010 09:19:21 UTC