Bug 25327
| Summary: | WebActionElementKey in navigation action information is based on a second hit-test, meaningless for non-mouse and synthetic events | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | mitz |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | darin |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
mitz
In the actionInformation dictionary passed to -webView:decidePolicyForAction:request:frame:decisionListener:, the value of WebActionElementKey is initialized from a hit-test result at the coordinates contained in the DOM event, if it is a mouse event. This is problematic because:
1) it results in misleading information for mouse events created in code. See http/tests/security/feed-urls-from-remote.html for example
2) it results in no information for non-mouse events, such as activating a link with the keyboard
3) the state when the second hit test is performed may be different from the state when the action took place
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
mitz
<rdar://problem/6816786>
mitz
<rdar://problem/3602728>