On Tue, Dec 16, 2008 at 7:32 PM, Brian Ellis <[email protected]> wrote: > > I may be repeating what Peter said to some extent, but unless I'm > missing something (and I may well be), the browser's security model > should prevent pages from referring to each other via JavaScript > across domain boundaries... so if the "page-modal" dialog also > "locked" all other tabs in the same tab group (which, as I understand > it, is defined as those tabs which share a domain) by graying out the > tab or otherwise indicating that it's unavailable, we could get 95% of > the way there with 5% of the headaches. It would be awesome if we > could perform some kind of analysis to determine that certain tabs are > independent of the locked page and not gray out those, but that seems > like a lot of work for not much extra benefit. The main thing here is > that user should not have to respond to the alert before they're > allowed to look at another page on a completely different domain; > anything that gets us that is, in my opinion, worth the time spent to > make it happen.
My disruptive use case: - Open calendar, move the browser window on a second monitor, bury it under a lot of more important windows. - Open gmail on the primary monitor, chat with someone from gmail, extract the chat window. - Wait for a calendar alert. This stops me from entering text in my talk window and there is nothing that alerts me the reason of why this is happening. It reminds me cooperative multitasking. :( M-A --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
