Bug Tracker

Modify ↓

Ticket #9554 (closed bug: worksforme)

Opened 2 years ago

Last modified 2 years ago

offset() fails in Chrome 12

Reported by: speednet Owned by:
Priority: low Milestone: 1.next
Component: offset Version: 1.6.1
Keywords: Cc:
Blocking: Blocked by:

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

comment:1 Changed 2 years ago by speednet

Update: Opera and Safari report 510 for the top, and IE and Firefox report 495. But Chrome 12 reports 0. Just to be precise!

comment:2 Changed 2 years ago by rwaldron

  • Priority changed from undecided to low
  • Resolution set to worksforme
  • Status changed from new to closed
  • Component changed from unfiled to offset

This appears to be fixed in Chrome 13 (dev)

comment:3 Changed 2 years ago by speednet

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 2 years ago by anonymous

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.

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

View ↑

Add a comment

Modify Ticket

Action
as closed
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.