WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
11628
REGRESSION (
r17597
): Command-return in text fields doesn't open a new tab or window
https://bugs.webkit.org/show_bug.cgi?id=11628
Summary
REGRESSION (r17597): Command-return in text fields doesn't open a new tab or ...
Daniele Metilli
Reported
2006-11-17 04:20:09 PST
In the old fields, command-click allowed the user to open a new tab or window. In the new ones, this doesn't work anymore.
Attachments
patch
(48.83 KB, patch)
2006-12-01 14:14 PST
,
Darin Adler
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
2006-11-18 02:04:16 PST
Could you please provide an example? I'm afraid I don't understand what the issue is.
Daniele Metilli
Comment 2
2006-11-18 02:26:56 PST
Oops, I meant Command-return, not Command-click! Example: 1 - Go to imdb.com 2 - Type something in the field on the left 3 - Command-return The resulting page will be loaded in the same tab, and it shouldn't.
Alexey Proskuryakov
Comment 3
2006-11-18 13:01:28 PST
Confirmed.
mitz
Comment 4
2006-11-21 09:12:17 PST
The regression is due to
r17597
, specifically "added DOM Event parameters to various functions so that the handlers can use the DOM Event instead of the global "current NSEvent";". The problem is that when a Command-Return keyboard event triggers a simulated click event, the click event doesn't inherit the modifiers from the mouse event. This affects not only form fields but also focused links, and breaks to the Option modifier as well. I think everything funnels through HTMLElement::click(), and in the relevant cases the caller to click() still has the original keyboard event which it could pass along if click() were modified to take it.
Darin Adler
Comment 5
2006-11-28 17:11:16 PST
Sounds like a good approach. I'll try to fix this.
Darin Adler
Comment 6
2006-12-01 13:44:03 PST
Got a patch -- writing release notes for review.
Darin Adler
Comment 7
2006-12-01 14:14:45 PST
Created
attachment 11706
[details]
patch
mitz
Comment 8
2006-12-01 14:51:00 PST
Comment on
attachment 11706
[details]
patch r=me
Darin Adler
Comment 9
2006-12-01 14:58:24 PST
Committed revision 17976.
Darin Adler
Comment 10
2006-12-01 14:58:44 PST
Note that this actually had nothing to do with native text fields!
mitz
Comment 11
2006-12-02 13:00:09 PST
Oops, Command-Return on a focused link is still broken.
mitz
Comment 12
2006-12-02 13:32:52 PST
(In reply to
comment #11
)
> Oops, Command-Return on a focused link is still broken. >
Two reasons for that. One is that HTMLAnchorElement::defaultEventHandler() neglects to pass the original event to dispatchSimulatedClick(). The other is that even if it did, findKeyStateEvent() stops at the simulated click event, which doesn't have the correct modifier state. I'm reopening this bug, but if you feel that a new bug is needed, just close this one again and I'll file a new one.
mitz
Comment 13
2006-12-02 13:51:26 PST
(Forgot to reopen)
mitz
Comment 14
2006-12-02 13:54:59 PST
Comment on
attachment 11706
[details]
patch Clearing the review flag to keep the bug from showing in the commit queue.
mitz
Comment 15
2006-12-04 22:42:42 PST
Darin fixed the "focused link" case in
r18012
(even though he would have preferred having a separate bug for that case!). Thanks, Darin!
mitz
Comment 16
2006-12-17 09:29:49 PST
Command-clicking a form's submit button is still broken. I will file a separate bug on that :-)
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug