Don't you like the idea of "click on the button", an extension slides out asking to confirm. When you click the "confirm" extension, you can go ahead with the action. This solves the problem of timeouts and it is more intuitive to a click interface than to non-click interface like the site i mentioned.
Also, why do you think setTimeout can't take a function reference... As far as i know, it can... Correct me if i am wrong. -GTG On 7/17/07, Stephan Beal <[EMAIL PROTECTED]> wrote:
On Jul 18, 3:56 am, "Dan G. Switzer, II" <[EMAIL PROTECTED]> wrote: <snip> > The trickiest part would be showing the user progress of the timer before > they can click to perform the action. > > The problem is I'm still not sure how intuitive this behavior would be. I > guess a clue/tool tip that explained how to use it could be used. All but the most basic of animations (incl tooltips) require additional plugins, though. i'm not sure if an animation like Highlight() would even work properly on a button?? i did see the wait-over-button-to-activate demo, and do find it interesting, but i also find the wait annoying (though i also think that all mail clients should have such a delay on the Send button to give us time to re-think it ;). i think that's suitable for certain problem domains but not all of them. i thought about adding a countdown timer and add the text to the button text, similarly to how Firefox does when you click an Install Addon link, but i find that too invasive and potentially problematic because it requires modifying the client's widget (button/span/ whatever) multiple times via set setTimeout(). i'm not a big fan of setTimeout(), partly due to its limitations (must take a string argument, instead of a function reference) and partly due to the philosophical incorrectness of allowing async code to run against unprotected objects. But... i also admit that this problem probably can't be solved without liberal use of setTimeout(). *Sigh*
