For what it's worth, I think the weirdness described in this thread is
a good reason not to try to make DOMContentLoaded consistent with the
load event for the sake of consistency. For one thing, the code that
manages the weirdness of the load event lives in a different place
compared to the code
On Thu, Jul 26, 2012 at 5:20 AM, Ian Hickson i...@hixie.ch wrote:
Thus, I propose a parallel mechanism in the form of an empty
element that goes in the head:
intent
action=edit intent action, e.g. open or edit, default share
type=image/png MIME type filter, default omitted,
On Thu, 2 Aug 2012, Henri Sivonen wrote:
This is a severe violation of the Degrade Gracefully design principle.
Adopting your proposal would mean that pages that include the intent
element in head would parse significantly differently in browsers that
predate the HTML parsing algorithm or
On Mon, 23 Jul 2012, Ian Hickson wrote:
So we could define the autocomplete= field's value as follows: [...]
I've now specced this, with some minor changes.
On Wed, 25 Jul 2012, David Holloway wrote:
A contact address might be helpful for sites that are non-commercial in
nature. Airlines
On Wed, Jul 25, 2012 at 10:20 PM, Ian Hickson i...@hixie.ch wrote:
Having carefully studied the Mozilla Web Activities proposal, the Web
Intents draft, the register*Handler APIs, and to a lesser extent the
dispatch mechanisms in existing operating systems (desktop and mobile) and
the piles
