Side navigation
#9554 closed bug (worksforme)
Opened June 09, 2011 01:47PM UTC
Closed June 09, 2011 04:45PM UTC
Last modified June 11, 2011 01:51AM UTC
offset() fails in Chrome 12
Reported by: | speednet | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | offset | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Elements without CSS positioning return an .offset().top of zero (0).
I created a JS Fiddle demonstrating this: http://jsfiddle.net/Speednet/ZVVfM/1/
Chrome 12 (12.0.742.91) reports zero(0) for .offset().top, all other browsers report 495.
Attachments (0)
Change History (4)
Changed June 09, 2011 01:50PM UTC by comment:1
Changed June 09, 2011 04:45PM UTC by comment:2
component: | unfiled → offset |
---|---|
priority: | undecided → low |
resolution: | → worksforme |
status: | new → closed |
This appears to be fixed in Chrome 13 (dev)
Changed June 09, 2011 07:11PM UTC by comment:3
I hear you, but it means my web sites won't work for Chrome users for the next 6-8 weeks, or however long it takes them to fix the bug in a stable release. Any ideas how I can at least patch jQuery until then?
Changed June 11, 2011 01:51AM UTC by comment:4
I am having the exact same issue. My site worked find until I upgraded to Chrome 12 a few days ago. If anyone knows a work around, please post.
Update: Opera and Safari report 510 for the top, and IE and Firefox report 495. But Chrome 12 reports 0. Just to be precise!