On Fri, 09 Oct 2009 08:42:12 +0200, Simon Pieters <[email protected]> wrote:
On Thu, 08 Oct 2009 23:19:28 +0200, Robert O'Callahan
<[email protected]> wrote:
On Fri, Oct 9, 2009 at 6:42 AM, Eric Carlson <[email protected]>
wrote:
I am not worried about the aesthetics of not having the event. I am
somewhat concerned about existing content that uses it (including many
of
the WebKit layout tests :-( ), but I think we will be better off in
the long
run if we get rid of the event and network state now.
Me too. I'm game if you are!
So I propose:
1) Remove the NETWORK_LOADED state and "load" and "loadend" events from
media elements.
'loadend' also fires after 'abort' and (when using the src attribute)
'error'. Should that stay as is, or also be removed?
Since we're going to contradict the progress events spec anyway, I would
suggest dropping all 'loadend' events. They're just not very useful.
The resource fetch algorithm simply never transitions from
step 2 to step 3.
2) Modify Gecko and Webkit accordingly.
If we do part 2, which I think is already permitted by the spec, then
authors will stop depending on "load" whether or not we get consensus
for
altering the spec.
Rob
--
Philip Jägenstedt
Opera Software
