Bug 65487

Summary: window.open behaves differently in onchange vs onclick event handlers
Product: WebKit Reporter: Brad Vogel <bradavogel>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Minor CC: bradavogel, leviw, leviw
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac (Intel)   
OS: OS X 10.6   
Attachments:
Description Flags
Test case
none
Test case (ignore previous) none

Brad Vogel
Reported 2011-08-01 14:35:52 PDT
Repro: 1) Open attached test.html in Chrome 12 2) Click "Open window google.com" button. A new tab will open. 3) Now click the selector and select "google.com". In step #3, the site will open as a new window (NOT a tab like step #2) and is vulnerable to the browser's popup blocker. Why does calling window.open with the same parameters in an onclick vs onchange behave differently?
Attachments
Test case (263 bytes, text/html)
2011-08-01 14:38 PDT, Brad Vogel 		no flags
Details
Test case (ignore previous) (282 bytes, text/html)
2011-08-01 14:46 PDT, Brad Vogel 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Levi Weintraub
Comment 1 2011-08-01 14:38:00 PDT
Please attach the test case ;)
Brad Vogel
Comment 2 2011-08-01 14:38:23 PDT
Created attachment 102559 [details] Test case
Brad Vogel
Comment 3 2011-08-01 14:38:55 PDT
(In reply to comment #1) > Please attach the test case ;) Attached :).
Levi Weintraub
Comment 4 2011-08-01 14:44:19 PDT
(In reply to comment #3) > (In reply to comment #1) > > Please attach the test case ;) > > Attached :). Is this the right file? It doesn't seem to correspond with your repro instructions.
Brad Vogel
Comment 5 2011-08-01 14:46:24 PDT
Created attachment 102560 [details] Test case (ignore previous)
Levi Weintraub
Comment 6 2011-08-01 14:49:30 PDT
This is a Chrome issue. Brad'll refile on crbug.com. Sorry for the extra bs, Brad!
Note You need to log in before you can comment on or make changes to this bug.