I've had a similar problem with version 1.3.1 ！
It was found in UI/Effects/Transfer. When target element with
display:none ,the function offset() return zero-valued top and left.
I've had found a temporary way to solve the problem.
/
jQuery.iUtil = {
getPosition
It is a feature indeed.
MDC points out to MSDN specs.
https://developer.mozilla.org/en/DOM/element.offsetWidth
http://msdn.microsoft.com/en-us/library/ms534304(VS.85).aspx
But it's a CSSOM documented feature:
http://www.w3.org/TR/cssom-view/#offset-attributes
The offsetHeight attribute, when ca
> Wow, that is sweet. For years I've had to deal with offsetWidth being
> 0 on hidden-by-parent elements, but never thought of using it as a
> feature!
Yeah, the tables have finally turned! We can use this stupid
bug/feature to our advantage.
--John
--~--~-~--~~~---~
Wow, that is sweet. For years I've had to deal with offsetWidth being
0 on hidden-by-parent elements, but never thought of using it as a
feature!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development"
> So, I've just tested this offset selector at IE6, IE7, FF3.0, Opera 9
> and Chrome. And it works as expected.
Cool, it certainly seems promising, at least. I think I'll tackle this
after 1.3.1 is landed.
--John
--~--~-~--~~~---~--~~
You received this message be
Oops, sorry for the invalid selector, so the right would be: $("div
span[offsetWidth!=0]");
(By the way, I've tested with > and it was working, I don' know why)
So, I've just tested this offset selector at IE6, IE7, FF3.0, Opera 9
and Chrome. And it works as expected.
Thanks a lot John, and I'm
Two quick things:
1) This selector isn't valid: $("div span[offsetWidth>0]"); (There's
no > in jQuery attribute selectors).
2) I really like the idea of checking the offsetWidth - that seems
much faster than what we're doing right now - and seems relatively
painless.
Could you file a bug on usi
