Opened 12 years ago
Closed 11 years ago
#9449 closed bug (patchwelcome)
offset fails in Chrome Extensions
Reported by: | ajpiano | Owned by: | ajpiano |
---|---|---|---|
Priority: | high | Milestone: | 1.next |
Component: | offset | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I'm working on getting a better (read: existent) testcase together for this, but it appears that jQuery.fn.offset fails when executed from within a Chrome Extension, when attempting to read the pageYOffset property of what jQuery believes to be the window, but is likely the Chrome Extension's isolated window which may not have all the properties we expect.
Change History (4)
comment:1 Changed 12 years ago by
Component: | unfiled → offset |
---|---|
Owner: | set to ajpiano |
Priority: | undecided → high |
Status: | new → assigned |
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
Chrome 12 definitely breaks the .offset() function. I've seen this reported elsewhere on the Web. An element must have relative position or else .offset().top will report zero (0).
comment:4 Changed 11 years ago by
Resolution: | → patchwelcome |
---|---|
Status: | assigned → closed |
Someone needs to write a test case and submit a patch. Chrome extensions aren't a formally supported or tested environment but if we can get a fix we can take a leap of faith that it works.
It's cool that you blew off writing a reduced test for this ;D