Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#5860 closed defect (fixed)

dojo._abs()/coords() doesn't account for borders of ancestor nodes (safari)

Reported by: bill Owned by: bill
Priority: high Milestone: 1.1
Component: HTML Version: 1.0
Keywords: Cc:
Blocked By: Blocking:

Description

This is the root cause of #5857. See attached test.

Attachments (2)

5860.html (1.1 KB) - added by bill 12 years ago.
test case
offsetTest.html (620 bytes) - added by bill 12 years ago.

Download all attachments as: .zip

Change History (5)

Changed 12 years ago by bill

Attachment: 5860.html added

test case

comment:1 Changed 12 years ago by bill

Summary: dojo._abs()/coords() doesn't account for borders on safaridojo._abs()/coords() doesn't account for borders of ancestor nodes (safari)

comment:2 Changed 12 years ago by bill

Resolution: fixed
Status: newclosed

(In [12454]) Fixes #5857, #5860: dojo.coords() wasn't accounting for borders an ancestor nodes (safari bug only) !strict

Changed 12 years ago by bill

Attachment: offsetTest.html added

comment:3 Changed 12 years ago by bill

I started to wonder if this was a safari bug... should offsetLeft/Top return coords relative to the border-box of the parent or content-box of the parent?

Well, FF and IE work the same as safari, returning relative to the content-box. Opera returns relative to the border box.

So I won't file a bug against Safari. I did upload offsetTest.html to test various browser behaviors. (If comboboxOffset is 10 or 12, then it's relative to the content-box of the parent. If it's about 60, then it's relative to the border-box).

Note: See TracTickets for help on using tickets.