- From: Joćo Eiras <joao.eiras@gmail.com>
- Date: Tue, 29 Apr 2008 19:29:02 +0100
- To: "Travis Leithead" <travil@windows.microsoft.com>
- Cc: "Web APIs WG (public)" <public-webapi@w3.org>
The user can easily and quickly close the dialog and then the main tab. Two clicks instead of one... don't be lasy :p. That's a non issue. It's much more preferable to have a native performant solution than relying on bloated js libraries, or code everything yourself. 2008/4/29, Travis Leithead <travil@windows.microsoft.com>: > > >> Most modality discussed so far has been about the view modality, ie > disallowing the user from accessing the original page content until > the dialog has been dismissed. Browser modality may also be about > not letting the browser unload/reload the page until a dialog has > been dismissed (eg "do you want to save before closing the window?"). > Is there any way to force a user to respond to a modal dialog > section before unloading the page? > If not, ideally a generic modality feature could be added to assist > both sections and current style HTML dialogs in achieving this > unload modality. > > > I'm not a big fan of allowing a web application to have that level of control of a user's browsing experience (a web page preventing a user from closing a tab, for example). The desktop paradigm is like allowing a program to prevent the user from restarting or shutting down the OS--seems like a bad design decision. > >
Received on Tuesday, 29 April 2008 18:35:46 UTC