Quantcast
Channel: jQuery: Ticket #13696: jquery.offset().top returns a different position in Firefox and Chrome
Browsing all 16 articles
Browse latest View live

Article 3

You have incorrect markup - span cannot contain div and the element you measure has div children which causes different behavior in Firefox (which doesn't extend span to contain div children) and...

View Article



Article 2

Replying to tylercrompton: Does this cause any unexpected behavior (other than the obvious difference in values)? No, but the answer the function gives back isn't correct (as far as I can measure).

View Article

Article 1

Does this cause any unexpected behavior (other than the obvious difference in values)?

View Article

Article 0

jsFiddle:  http://jsfiddle.net/aPVK2/

View Article

Article 6

No, the bottom is in the same position, top differs. Open Firebug & Chrome Web Inspector and you'll see.

View Article


Article 5

I understand, but the top of the element is at the same position in different browsers. That the height of the element has a different value, shouldn't make a difference, right?

View Article

status changed; resolution set

status changed from new to closedresolution set to notabug I'm closing it since it's caused by real difference in element sizes and positions in these browsers so jQuery correctly shows the difference.

View Article

Article 7

You are correct indeed, the span is only around 20 pixels in height. I can fix this myself with a wrapper div, thanks for your time!

View Article


Article 7

You are correct indeed, the span is only around 20 pixels in height. I can fix this myself with a wrapper div, thanks for your time!

View Article


Article 6

No, the bottom is in the same position, top differs. Open Firebug & Chrome Web Inspector and you'll see.

View Article

Article 5

I understand, but the top of the element is at the same position in different browsers. That the height of the element has a different value, shouldn't make a difference, right?

View Article

status changed; resolution set

status changed from new to closedresolution set to notabug I'm closing it since it's caused by real difference in element sizes and positions in these browsers so jQuery correctly shows the difference.

View Article

Article 3

You have incorrect markup - span cannot contain div and the element you measure has div children which causes different behavior in Firefox (which doesn't extend span to contain div children) and...

View Article


Article 2

Replying to tylercrompton: Does this cause any unexpected behavior (other than the obvious difference in values)? No, but the answer the function gives back isn't correct (as far as I can measure).

View Article

Article 1

Does this cause any unexpected behavior (other than the obvious difference in values)?

View Article


Article 0

jsFiddle: ​http://jsfiddle.net/aPVK2/

View Article
Browsing all 16 articles
Browse latest View live




Latest Images