On Thu, Dec 18, 2008 at 11:25 AM, Darin Fisher <[email protected]> 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.) > 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. 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? PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
