Bug 16960 – webView:decidePolicyForNavigationAction:request:frame:decisionListener returns incorrect value for WebActionElementKey -> WebElementDOMNode key in policy when the frame's scroll position is different than the initial value

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: New Bugs

[Benjamin Jackson]

I have a delegate set up to catch links when the user clicks them in a WebView.

This delegate pulls the value of [[policy objectForKey:@"WebActionElementKey"] objectForKey:@"WebElementDOMNode"] to determine the node which was clicked, then executes an action based on the result.

If the user scrolls the WebView down one or more lines, the WebView appears to not take into account the vertical offset caused by the scrolling, and instead of containing the node of the link which was clicked, the dictionary contains the node which would be returned if the user had clicked above the area which was actually clicked.

This bug is consistently reproduceable.

[Mark Rowe (bdash)]

This is a duplicate of bug 15780.

Unrelated to the bug, but note that WebActionElementKey and WebElementDOMNode are named constants so you should be calling [[policy objectForKey:WebActionElementKey]
objectForKey:WebElementDOMNode] rather than using them as string literals.

*** This bug has been marked as a duplicate of 15780 ***

[Benjamin Jackson]

Thanks Mark, apologies for the duplicate. Glad to see it's fixed :)