-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 e. roman wrote:
> Goal: > Make alerts less annoying by reducing their scope from application modal > to tab-modal. > > Problems: > There is not necessarily a 1:1 mapping between javascript environments > and tabs/windows. For example, popup windows, and the tab which spawned > them share the same environment. So if either the tab or one of its > popups calls alert(), ALL of those windows must be suspended, and block > on the modal dialog. So far this sounds reasonable. > This gets hairier when you consider renderer process boundaries. Unlike > other browsers, chrome (mostly) has tabs running in separate processes, > which means they have their own thread and js environment. This isn't > the whole story though, for a number of reasons pages may run in the > same renderer process. This means they share the same javascript > thread, This is not clear to me. Can you give an example how and when it can happen that two different Tabs in the browser share the same JavaScript-Thread? > and when any one of them blocks, the others will be blocked too. > So while you only want to block Tab1 and popup1 when an alert happens, > you may end up having to block Tab2, Tab3, Tab4 as well! > (and communicating to the user why this other stuff is blocked too, can > easily become confusing). Yes this is confusing me, because I really see no reason why one website/web-application should block another. > Note even when tabs are not in the same renderer, there are still UI > challenges in conveying a set of windows blocked by a modal dialog. > (Since it may be the tab has some children popups). You now need to > associate the dialog with a set of windows, and make it clear why they > are blocked, and which window an alert originates from (security concern). > [...] I would suggest the following: All tabs that are blocked because their Javascript is waiting in an alert() become greyed out and the alert box with the ok button is drawn above *all* of them (not as a top level window, just a rectangle inside the Window/tab) and the tab/titlebar/taskbaricon will flash until one of the OK-Buttons for this alert is clicked. - -- private communication within hostile networks: http://torchat.googlecode.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIxGHTxT6R4jlFoh0RAu7aAJ4026Wgr4UuDXL4fcA5k3RoLDTUNgCggy5b 0U9q3pKKX+1ASYPeaJsF8nA= =Pzz1 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
