#9554 closed bug (worksforme)
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.
Change History (4)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
| Component: | unfiled → offset |
|---|---|
| Priority: | undecided → low |
| Resolution: | → worksforme |
| Status: | new → closed |
This appears to be fixed in Chrome 13 (dev)
comment:3 Changed 9 years ago by
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?
comment:4 Changed 9 years ago by
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.
Note: See
TracTickets for help on using
tickets.
Update: Opera and Safari report 510 for the top, and IE and Firefox report 495. But Chrome 12 reports 0. Just to be precise!