New issue
Advanced search Search tips

Issue 797828 link

Starred by 1 user
Status: Assigned
Owner:
nzolghadr@chromium.org
Cc:
sadrul@chromium.org
dtapu...@chromium.org
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Investigate why blink hit test may return null as the result

Project Member Reported by nzolghadr@chromium.org, Dec 27 2017 
It looks like in some cases blink hit test API may return null.
Maybe due to the fact that it needs to do a layout before finding the target. If so we may need to trigger the layout and then return the result of the hit test or something like that.
Issue 797654 is related to this problem.

Comment 1 by nzolghadr@chromium.org, Jan 3 2018 

It does seem that we already do a layout before hittest all the time. Except one case: when this is the first layout:
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/input/EventHandler.cpp?gsn=HitTestResultAtPoint&l=278

So in that case we return null indicating that there hasn't been any layout and user technically should not be able to interact with the page. I assume browser can ask that renderer about the target in that case. Right? What should we do in that case?
►

Sign in to add a comment