On Thu, 11 Feb 2010, Ojan Vafai wrote:
>
> Currently, modal dialogs that fire during beforeunload/unload events are
> used to confuse users into not being able to leave websites (e.g. to
> tell the user to click on the wrong button for in the browser's
> beforeunload alert dialog). They also add
On Mon, Feb 15, 2010 at 3:37 PM, Mike Hearn wrote:
> Browsers could solve the editor use case by treating "close tab" as
> "hide tab" for a minute or two before actually shutting down the page.
Firefox today has undo close tab. And people have joked for years
about undo quit application (I think
On Mon, Feb 15, 2010 at 2:29 AM, Biju wrote:
> I dont know whether you all saw list of people on
> https://bugzilla.mozilla.org/show_bug.cgi?id=391834
> https://bugzilla.mozilla.org/show_bug.cgi?id=61098
Those two address a *completely* separate issue, that of someone
running an infinite alert()
Browsers could solve the editor use case by treating "close tab" as
"hide tab" for a minute or two before actually shutting down the page.
Then the problem becomes, how do you make it obvious to users that
they can get their work back by pressing a magic button somewhere?
The modal quit loop is f
I dont know whether you all saw list of people on
https://bugzilla.mozilla.org/show_bug.cgi?id=391834
https://bugzilla.mozilla.org/show_bug.cgi?id=61098
Though I'm not sure what exactly Ojan is proposing we forbid?
I think his suggestion is to forbid all of window.prompt, window.alert,
and window.showModalDialog. Persumably window.confirm as well.
Exactly. But we don't need a spec to tell that. It's 100% user agent
feature, so you're f
2010/2/11 Jonas Sicking
> 2010/2/11 Scott González :
> > I use dialogs in this fashion as well. Users get very frustrated when
> they
> > accidentally leave a page with unsaved content and this is the easiest
> > improvement for most developers to make.
>
> However you can accomplish this using t
On Feb 11, 2010, at 7:42 PM, Jonas Sicking wrote:
2010/2/11 Scott González :
On Thu, Feb 11, 2010 at 9:55 PM, Tab Atkins Jr.
wrote:
I commonly see them put to *good* use by editting applications,
warning you if you attempt to leave the page without saving. It has
saved me from accidental
2010/2/11 Scott González :
> On Thu, Feb 11, 2010 at 9:55 PM, Tab Atkins Jr.
> wrote:
>>
>> I commonly see them put to *good* use by editting applications,
>> warning you if you attempt to leave the page without saving. It has
>> saved me from accidentally lost effort just in the past few days in
On Thu, Feb 11, 2010 at 9:55 PM, Tab Atkins Jr. wrote:
> I commonly see them put to *good* use by editting applications,
> warning you if you attempt to leave the page without saving. It has
> saved me from accidentally lost effort just in the past few days in
> both my email and one of my wikis.
On Thu, Feb 11, 2010 at 8:25 PM, Ojan Vafai wrote:
> Currently, modal dialogs that fire during beforeunload/unload events are
> used to confuse users into not being able to leave websites (e.g. to tell
> the user to click on the wrong button for in the browser's beforeunload
> alert dialog). They
Currently, modal dialogs that fire during beforeunload/unload events are
used to confuse users into not being able to leave websites (e.g. to tell
the user to click on the wrong button for in the browser's beforeunload
alert dialog). They also add a layer of complexity to browser shutdown
behavior.
12 matches
Mail list logo
