Skip to main content

Bug Tracker

Side navigation

#6237 closed bug (invalid)

Opened March 06, 2010 11:48PM UTC

Closed April 17, 2011 06:39PM UTC

Setting offset of an object which isn't in DOM failed to take scroll into account

Reported by: AzaToth Owned by:
Priority: undecided Milestone:
Component: offset Version: 1.4.2
Keywords: needsreview Cc:
Blocked by: Blocking:

If having an element out of DOM and we have parent scrolled and is setting offset, the scroll in question isn't taken into account, and the object gets wrong offset.


Attachments (0)
Change History (4)

Changed March 07, 2010 01:20AM UTC by AzaToth comment:1

Per it looks like that $.curCSS is the general problem.

Changed November 12, 2010 02:40AM UTC by snover comment:2

milestone: 1.4.3

Resetting milestone to future.

Changed November 20, 2010 10:27PM UTC by snover comment:3

keywords: → needsreview
priority: → undecided

test case demonstrates that the offset that gets set is pretty funky when an element is detached from the document. I’m not actually sure that this is a bug, since technically there is no document for the offset to be relative to when the element is detached.

Changed April 17, 2011 06:39PM UTC by john comment:4

resolution: → invalid
status: newclosed

Yeah, agree with snover. There really is no offset if the element isn't actually in the page.