Ticket #5860 (closed defect: fixed)

Opened 9 months ago

Last modified 9 months ago

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

Reported by: bill Owned by: bill
Priority: normal Milestone: 1.1
Component: HTML Version: 1.0
Severity: normal Keywords:
Cc:

Description

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

Attachments

5860.html (1.1 kB) - added by bill 9 months ago.
test case
offsetTest.html (0.6 kB) - added by bill 9 months ago.

Change History

Changed 9 months ago by bill

test case

Changed 9 months ago by bill

  • summary changed from dojo._abs()/coords() doesn't account for borders on safari to dojo._abs()/coords() doesn't account for borders of ancestor nodes (safari)

Changed 9 months ago by bill

  • status changed from new to closed
  • resolution set to fixed

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

Changed 9 months ago by bill

Changed 9 months 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.