- From: Charles McCathieNevile <charles@w3.org>
- Date: Fri, 9 Mar 2001 12:19:53 -0500 (EST)
- To: Matt May <mcmay@bestkungfu.com>
- cc: Anne Pemberton <apembert@erols.com>, WAI <w3c-wai-gl@w3.org>
Currently the Stop button doesn't stop everything as far as I know - as Matt says, scripts are a different case. So the requirement on a User Agent needs to be "make the page sit still, and it shouldbe clear that this includes motion effects due to scripting. I think it mostly is, but I will take an action item to look at that if someone promises to remind me in a few days that I said I would. Charles On Thu, 8 Mar 2001, Matt May wrote: ----- Original Message ----- From: "Anne Pemberton" <apembert@erols.com> > Doesn't the Stop button stop all everything on the page? If so, what is > the problem? Does stop not exist or work the same way in all browsers? In the case of the walking ants, the Stop button can't control that. All it controls in IE on Windows, for example, is embedded audio and animated GIFs. It's not a standard. Actually, the Stop button itself isn't even a standard insofar as it's a user-agent widget. UAAG would have to specify its behavior, and even then, the walking-ants analogy would probably sneak through, as the Stop button would have to stop script execution on the page to stop the motion of the ants, and there's no way to selectively disable scripts or (that I'm aware of) to force cleanup/garbage collection on any given script. - m -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +1 617 258 5999 Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Friday, 9 March 2001 12:20:09 UTC