Skip to main content

Bug Tracker

Side navigation

#8877 closed bug (wontfix)

Opened April 14, 2011 06:07PM UTC

Closed July 12, 2011 03:11PM UTC

Firefox 3.6 and 4 reports different values for position when translate is present on an element

Reported by: timmywil Owned by:
Priority: high Milestone: 1.next
Component: offset Version: 1.5.2
Keywords: position, firefox Cc:
Blocked by: Blocking:
Description

Firefox's getBoundingClientRect(), which we use in offset, does not account for translations.

test case

Attachments (0)
Change History (6)

Changed April 14, 2011 06:08PM UTC by timmywil comment:1

component: unfiledoffset
keywords: → position, firefox 4
priority: undecidedlow
status: newopen

Changed April 14, 2011 06:24PM UTC by rwaldron comment:2

priority: lowhigh

totes confirmed

Changed April 14, 2011 06:53PM UTC by anonymous comment:3

Same on firefox 3.6.x

Changed April 14, 2011 07:08PM UTC by timmywil comment:4

description: Firefox 4's getBoundingClientRect(), which we use in offset, does not account for translations. \ \ [http://jsfiddle.net/timmywil/K2Q67/ test case]Firefox's getBoundingClientRect(), which we use in offset, does not account for translations. \ \ [http://jsfiddle.net/timmywil/K2Q67/ test case]
keywords: position, firefox 4position, firefox
summary: Firefox 4 reports different values for position when translate is present on an elementFirefox 3.6 and 4 reports different values for position when translate is present on an element

Changed July 04, 2011 08:43PM UTC by anonymous comment:5

This is really similar to http://bugs.jquery.com/ticket/8362

Changed July 12, 2011 03:11PM UTC by rwaldron comment:6

resolution: → wontfix
status: openclosed

Firefox 4 is no longer supported by Mozilla and Firefox 3.6 is scheduled for End-Of-Life