Re: Moving Form Events from DOM3 Events to HTML5

On Mon, 05 Oct 2009 20:38:40 -0400, Ian Hickson <ian@hixie.ch> wrote:

> Consider 'resize' or 'scroll':
> # A user agent must dispatch this event when a document view or an  
> element
> # has been resized/scrolled. This event type is dispatched after the
> # resize/scroll has occurred.
> * Do these events fire synchronously, or are they queued up?
> * The text says that they fire at the end of the resize/scroll, but what
> is the end? (In particular, they seem to fire continuously in the UAs I
> tested.)

You probably already know, but just in case:

On WinXP at least, how 'resize' fires depends on the Windows "Show windows  
contents while dragging" option in Display Properties -> Appearance ->  
Advanced.

If the contents are shown, it fires as you're dragging (with some  
coalescing of the events I think). If the contents are not shown, it fires  
after and maybe just once. However, in FF 2.x (maybe it was 1.x though) I  
think, it ignored this option and always fired just once no matter what.  
FF3 latest trunk seems to honor the Windows setting though.

I haven't reverse-engineered the exact behavior, but that Windows setting  
does/did make difference in some browsers. And, I think with IE, there's a  
way to make it goof up th resize event, but unfortunately, I don't  
remember how to trigger it. Maybe it has something to do with using  
setTimeout.

I also think you used to be able to capture resize events from an iframe  
in the main document in Opera using true for addEventListener. Or, maybe  
that was just Opera making resize bubble to multiple targets.

-- 
Michael

Received on Tuesday, 6 October 2009 10:35:48 UTC