Bug 3638
| Summary: | Command-click modifier gives unexpected behavior in multiple-<select> linked to iframe form submission | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Devin Chalmers <devin.chalmers> |
| Component: | Forms | Assignee: | Dave Hyatt <hyatt> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ian, mitz |
| Priority: | P2 | ||
| Version: | 412 | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://lrcd.com/sound/test.php | ||
Devin Chalmers
A multiple-select box is wired up with Javascript to submit its form to an iframe on the same page when
the user selection is changed. However, the Safari command-click behavior of loading form submissions in
a new tab prevents Safari users from selecting multiple discontinuous entries in either <select> box.
Instead of loading in the iframe, the form submission loads into a new tab.
The bug appears when holding command and clicking, as well as with a middle-click on a three-button
mouse and the default Tiger mouse settings.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Devin Chalmers
I guess the iframe isn't really relevant, I can imagine situations where a multiple selection would submit a
form to the main viewport and this behavior would still be undesirable. Should the command-click new-
tab(/new window) behavior be modified on multiple selection boxes?
Joost de Valk (AlthA)
Confirmed, weird stuff :)
mitz
This issue was resolved in r17597, however it is considered as a regression -- see bug 11858.
Darin Adler
My fix for bug 11858 does not re-introduce this bug, so we can mark this as fixed!