Status: Untriaged Owner: [email protected] CC: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 25357 by [email protected]: Need to deal with non-SSL reads from shared workers http://code.google.com/p/chromium/issues/detail?id=25357 http://code.google.com/p/chromium/issues/detail?id=20176 describes an issue with dedicated workers - non-SSL reads from dedicated workers were not reflected in the parent window's lock icon. We may need to do something similar for shared workers - propagate this error around to every related window. It gets a little iffy, though - since shared workers are only connected to windows via MessagePorts, why do we treat SharedWorkers specially? If two arbitrary windows are connected via a MessagePort, and one window does a non-SSL read, should that pollute the other window too (i.e. why are we treating non-SSL reads from a worker differently than non-SSL reads from a connected window)? This probably impacts globalscript as well. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
