Status: Untriaged Owner: [email protected] Labels: Type-Feature Pri-2 OS-All Area-WebKit
New issue 6363 by [email protected]: Popup blocker whitelisting/heuristic improvements http://code.google.com/p/chromium/issues/detail?id=6363 On at least some sites, our popup blocker makes it painful to use the site, because we don't or can't catch "user-initiated" popups as such. It's not yet clear whether we'd need better heuristics, some sort of whitelisting/granular control, or what, so before designing a solution, I'm simply collecting example sites where Chrome is painful right now. * Visit http://disneyworld.disney.go.com/wdw/index?bhcp=1 and click in the page's upper navigation bar where it says "map". This causes a navigation to a new HTML page which auto-opens a popup and then does history.go(-1);. The best heuristic I could think of for this is "allow onload popups for pages loaded by a user-gesture, whose origin page was within the same site". erg thinks this is still pretty exploitable. * Visit http://www.in2art.com/art-supplies/sharpie-markers and click on one of the products. Not sure exactly why the resulting popup gets blocked. -- 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 -~----------~----~----~----~------~----~------~--~---
