Quoting myself:
> You could always fallback on a regular alert for page refreshes and
> the like.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email
> But what about situation when someone type new url , press home button
> or one from favourites toolbar?
That's the "You could always fallback on a regular alert for page
refreshes and the like." bit.
-- T.J.
On Mar 10, 10:17 am, Quleczka wrote:
> > There's another, less bullet-proof solutio
> There's another, less bullet-proof solution, which involves catching
> and stopping all click (an possibly keypress) events on links.
But what about situation when someone type new url , press home button
or one from favourites toolbar?
Quleczka
--~--~-~--~~~---~-
There's another, less bullet-proof solution, which involves catching
and stopping all click (an possibly keypress) events on links.
That would allow for a custom dialog.
You could always fallback on a regular alert for page refreshes and
the like.
Best,
Tobie
On Mar 9, 9:39 pm, Quleczka wrot
My first thought was gmail scenario as well :)
Even google use just confirmation dialog...I've never seen any other
type - so I guess you have to live with it ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Proto
Thank you so much for your response T.J.
I emailed my work friends the same question. It hit me yesterday. My
friend was like why don't you create your own window. Then I realized that
in showing and hiding divs we're just manipulating the dom and that like you
said the browser doesn't know to s
Hi,
The reason that using it with the unload doesn't work is that it
doesn't stop execution at the point it's shown the way alert and
confirm do. As far as I know, only built-in things like alert and
confirm can do that. Consequently, you show the dialog, but then the
browser continues with wha
