by the way, we already auto-dismiss alerts that have been generated too frequently. -Darin
On Thu, Dec 18, 2008 at 11:47 AM, Charles Reis <cr...@chromium.org> wrote: > > > On Thu, Dec 18, 2008 at 11:30 AM, Peter Kasting <pkast...@google.com>wrote: > >> On Thu, Dec 18, 2008 at 11:25 AM, Darin Fisher <da...@chromium.org>wrote: >>> >>> This idea is similar to what happens today when one tab runs a >>> synchronous XMLHttpRequest that takes a long time to complete. The other >>> tabs in the same renderer become mysteriously unresponsive. >>> >> >> (I would love to do something for this too! Maybe we can gradually dim >> the tabs or something.) >> > > This is true for any type of script unresponsiveness. Right now, we > eventually show the "taking too long" dialog. > > >> >> >>> How is the user to find said tab? Maybe all tabs in the tab group get >>> some UI that allows the user to switch to said tab, or maybe interacting >>> with a tab in the tab group rips you away to the magical background tab? >>> >> >> These sorts of things are precisely what we were proposing, yes. >> > > Right-- I'd be more inclined to have UI that lets the user switch to the > tab than automatically taking them there. I agree it's a little > unconventional, but it matches what's going on under the hood. > > >> Why do we want to do so much work to support something suboptimal like >>> this? Why not try to do something cleaner (and more predictable) like >>> auto-dismiss background alerts? >>> >> >> I'm OK with doing something better (and believe I said so), though you'd >> need to make sure this actually solves all use cases. For example, what >> about prompts, which have the same modality problems as alerts but perhaps >> can't be easily dismissed? Do we just punt that because these are less >> frequent? And how do users see notifications from these dismissed alerts? >> > > I'm torn. On the one hand, there are clearly relationships between some > tabs that will become visible in one way or another-- crashes, > unresponsiveness, modal dialogs, task manager, etc. Finding a good way to > convey these relationships seems valuable to me, and would provide (what I > think is) a clean solution to the dialog problem. I agree with Peter that > these relationships can be somewhat rare, but they will happen. > > On the other hand, it's a smaller change to take the auto-dismiss approach > and try to hide the relationships between tabs under the rug. I only think > it works well for a standard alert and not for prompts that request an > answer, because auto-dismissing those will change the behavior (i.e. break) > exiting pages. > > If we do auto-dismiss alerts, an infobar in your current tab or a taskbar > toast seem appropriate. (I prefer the taskbar toast, because you might not > even be using the browser at the time.) > > What if we auto-dismiss informational alerts (not those that expect an > answer) for now, and talk with Glen/Ben about UI ideas for longer term ways > of showing relationships between the tabs in a site instance? > > Charlie > > > >> PK >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
