Stephan, In the demo, once i click, the action gets cancelled too quickly before i understand that i need to click it again... Also, i guess it is pretty difficult to explain this to the user...
There should be some other way, instead of just time before which the event is cancelled. Just thinking out loud, maybe something like clicking outside the button cancels it... i dont know.... I know, we can increase the timing there, but still, i am not sure if the "timing" approach is the best for "confirm" kinda dialog. For "undo" style dialogs that probably is a better idea... Just something to ponder... -GTG On 7/17/07, Stephan Beal <[EMAIL PROTECTED]> wrote:
On Jul 18, 12:47 am, Felix Geisendörfer <[EMAIL PROTECTED]> wrote: > Cool idea. Just add support for a class that's being added to the button > when in 'confirm' mode - otherwise there is no way to visually highlight > this new UI approach for the user ; ). My initial thought was to use an onclick callback so the user could modify the element using an arbitrary animation, but you're right - adding a class is a good generic solution without the usage overhead of a callback. i've added this to the TODO list. Thanks :).
