[Webkit-unassigned] [Bug 65412] New: beforeload event doesn't block the resource correctly: it reloads over and over

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=65412

           Summary: beforeload event doesn't block the resource correctly:
                    it reloads over and over
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
               URL: http://movies.nytimes.com/2011/07/29/movies/cowboys-al
                    iens-with-daniel-craig-review.html
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: fam.lam at live.nl


Summary:
A beforeload event is fired over and over all the time when the resource is blocked

Steps to Reproduce:
1. install AdBlock (http://safariadblock.com/ or for Chrome https://chrome.google.com/webstore/detail/gighmmpiobklfepjocnamgkkbiglidom). Disable all filter lists except for EasyList in it's options page (accessible via the button on the toolbar)
2. visit http://movies.nytimes.com/2011/07/29/movies/cowboys-aliens-with-daniel-craig-review.html
3. open the developer tools (by choosing inspect element on the page). Go to the tab 'profiles' and run a CPU profile. Notice the function 'canload' (safari.self.tab.canLoad, directly called from the beforeload event) from the source code is  called over and over all the time (resulting in high CPU usage).
4. Insert a breakpoint in the injected script 'adblock_start.js' in the function beforeloadHandler (in the line 'var el = event.target'). Notice it's always the same resource (http://graphics8.nytimes.com/ads/images/misc/spacer.gif) being loaded.

Expected Results:
Blocking the resource does block the resource

Actual Results:
Blocking the resource results in the resource being reloaded

Happens in both Chrome and Safari.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.