Summary: | REGRESSION: cursor tracking and hit testing in scrollable block don't take borders into account | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | mitz | ||||||
Component: | Layout and Rendering | Assignee: | Beth Dakin <bdakin> | ||||||
Status: | VERIFIED FIXED | ||||||||
Severity: | Normal | CC: | bdakin, vicki | ||||||
Priority: | P1 | ||||||||
Version: | 420+ | ||||||||
Hardware: | Mac | ||||||||
OS: | OS X 10.4 | ||||||||
Attachments: |
|
Description
mitz
2005-11-25 14:31:52 PST
Created attachment 4800 [details]
testcase
I suspect that this is a regression from the fix for <rdar://problem/3885711> (bug 4047). In particular, the changes to RenderLayer::hitTestLayer which introduced borderLeft() and borderBottom() there. Created attachment 4801 [details]
don't add left and bottom borders when hit-testing
Comment on attachment 4801 [details] don't add left and bottom borders when hit-testing I checked that this doesn't affect the testcase for bug 4047. Comment on attachment 4801 [details]
don't add left and bottom borders when hit-testing
r=me
Is there any way we could make a test case for this? A DumpRenderTree test case, that is. We have support for moving the mouse... There is probably a way to get the current cursor from JavaScript, if not, we could add that functionality to DumpRenderTree's layoutTestController I don't think it's easy to add querying the cursor to DumpRenderTree -- the OS doesn't even have a good way to inspect the current cursor. But we can make a test that relies on hit testing rather than the cursor. I committed this change. I added the attached test case to the manual tests directory until we can find a better solution. I should have made a more extensive testcase -- this is still (or has become) broken in certain conditions. I am going to file a new bug. |