Bug 87341

Summary: QWebHitTestResult::element behavior different from InspectorDOMAgent
Product: WebKit Reporter: Jared Flatow <jflatow>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: allan.jensen
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Makes the returned Qt hit test element match the behavior of WebInspector. none

Jared Flatow
Reported 2012-05-23 22:15:19 PDT
When trying to access an element via a 'hit test' through the Qt bindings, there is no way to get the same behavior as with the normal WebKit inspector. An empty hit result is returned if the hit element is not an element node, whereas webkit would access the parent node in this case. The attached patch addresses this discrepancy.
Attachments
Makes the returned Qt hit test element match the behavior of WebInspector. (802 bytes, patch)
2012-05-23 22:16 PDT, Jared Flatow 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Jared Flatow
Comment 1 2012-05-23 22:16:53 PDT
Created attachment 143729 [details] Makes the returned Qt hit test element match the behavior of WebInspector.
Antonio Gomes
Comment 2 2013-12-12 02:18:45 PST
it needs unit test and a changelog entry. see http://www.webkit.org/coding/contributing.html
Alexey Proskuryakov
Comment 3 2013-12-12 09:15:35 PST
Also, the Qt port no longer exists on trunk, and this patch looks like a chromium one.
Note You need to log in before you can comment on or make changes to this bug.