- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 29 Apr 2008 16:30:51 -0700
- To: Joćo Eiras <joao.eiras@gmail.com>
- CC: Web APIs WG <public-webapi@w3.org>
The shaded page, no doubt about it. The shaded page lets me close that window/tab. The shaded page doesn't clutter my windows task bar. The shaded page doesn't interfere if I'm busy in some other app or tab at the time. / Jonas Joćo Eiras wrote: > > > What would you rather prefer: > - a native window which you (or your UA) can easily control ? > - a shaded page with some floating content which you can't close at > will or control ? > > I obviously agree with the downside of having either modal or non-modal > window begin opened from webpages, but there are alternatives, and many > can reduce user experience and anoy developers with extra layers of > libraries and/or APIs. > There's little you can do againast it :p > > > Jonas Sicking <jonas@sicking.cc> escreveu: > >> Joćo Eiras wrote: >>>> Unless the page raises another dialog of course >>> For that there are popup blockers. >>> The user must click something for another popup to open. >>> 2008/4/29, Bjoern Hoehrmann <derhoermi@gmx.net>: >>>> * Joćo Eiras wrote: >>>> >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. >>>> >>>> >>>> Unless the page raises another dialog of course, either maliciously or >>>> due to a coding problem. Preventing that from happening would probably >>>> not be easy without some surprises. >> >> Popup blockers are there to try to mitigate an evilness that was added >> a long time ago in a more innocent (naive?) time. >> >> Lets not add more such evilness. It only forces ourselves to struggle >> to find decent mitigation techniques, and forces developers to try to >> deal our mitigation techniques. >> >> / Jonas >> > > >
Received on Tuesday, 29 April 2008 23:32:16 UTC