- From: Ryosuke Niwa <rniwa@webkit.org>
- Date: Tue, 10 May 2011 18:39:11 -0700
- To: www-dom@w3.org
- Cc: Ojan Vafai <ojan@chromium.org>, Erik Arvidsson <arv@chromium.org>, Glenn Maynard <glenn@zewt.org>
Received on Wednesday, 11 May 2011 01:39:58 UTC
I talked with my colleagues and we came to a conclusion that WebKit should match IE's and FF's behaviors since we couldn't think of a reason why either behavior is better. I filed a WebKit bug https://bugs.webkit.org/show_bug.cgi?id=60600 to track this behavioral change. As such, please consider spec'ing this behavior explicitly. - Ryosuke On Sun, May 8, 2011 at 8:15 PM, Glenn Maynard <glenn@zewt.org> wrote: > On Sun, May 8, 2011 at 11:12 PM, Ryosuke Niwa <rniwa@webkit.org> wrote: > >> On Sun, May 8, 2011 at 8:01 PM, Glenn Maynard <glenn@zewt.org> wrote: >>> >>> In all cases matching Firefox, if the node is removed and immediately >>> reinserted at the same position, the behavior is unchanged: onclick doesn't >>> happen. (In other words, they're remembering that the node was removed, not >>> checking that it's still in the document later.) >>> >> >> Is this Internet Explorer's behavior? >> > > Yes, IE9 matches FF4. (I typed that out, but it seems to have escaped from > the message.) > > -- > Glenn Maynard >
Received on Wednesday, 11 May 2011 01:39:58 UTC