Side navigation
#9449 closed bug (patchwelcome)
Opened May 27, 2011 10:09PM UTC
Closed June 26, 2012 02:02AM UTC
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.
Attachments (0)
Change History (4)
Changed May 27, 2011 10:11PM UTC by comment:1
component: | unfiled → offset |
---|---|
owner: | → ajpiano |
priority: | undecided → high |
status: | new → assigned |
Changed May 27, 2011 10:12PM UTC by comment:2
It's cool that you blew off writing a reduced test for this ;D
Changed June 08, 2011 11:19PM UTC by comment:3
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).
Changed June 26, 2012 02:02AM UTC by comment:4
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.