Quantcast
Channel: jQuery: Ticket #6446: Mobile Safari 4.0.4: $.offset.top() reports wrong position after scroll
Browsing latest articles
Browse All 34 View Live

Article 16

Replying to edwincheese: +1 Same issue as reported in JQuery forum: ​http://forum.jquery.com/topic/offset-returns-incorrect-values-in-ipad

View Article



status, milestone changed; resolution set

status changed from open to closedresolution set to fixedmilestone changed from 1.next to 1.9 This works in latest ​http://jsbin.com/ofoqoc/6/edit

View Article

Article 14

Reduced Test case that shows the bug in IOS 4.0.2 and others.​http://jsbin.com/ofoqoc/5

View Article

Article 13

"test a mobile web-app in Chrome" any suggestions?

View Article

Article 12

This actually occurs on the desktop as well... test a mobile web-app in Chrome by scrolling and then clicking on your target -- gets the same result as mobile safari.

View Article


priority changed; milestone set

priority changed from undecided to highmilestone set to 1.next

View Article

Article 10

For all those using the workaround function hack, you *might* want to test result for null before you start subtracting. (I had some poorly behaved code that happens to call offset and get a null. The...

View Article

milestone deleted

milestone1.4.3 deleted Resetting milestone to future.

View Article


Article 8

I've found that calculating the offset with straight javascript seems to work. Test page:​http://mark.antsclimbtree.com/files/jquery.ipad-test.php Clicking the yellow square shows the top and left as...

View Article


Article 7

Just thought I'd add my own little detection JS to the mix. It's a lot smaller than others but relies completely on the user agent string:​https://gist.github.com/661844#comments

View Article

status changed; priority set

priority set to undecidedstatus changed from new to open

View Article

Article 5

rty I've added an extra test vs iOS version since the bug occurs only on 3.2-4.0.x, 4.1 is not affected. Feel free to add the following test condition to your snipplet: /; CPU.*OS...

View Article

Article 4

Thanks matas for good decision!

View Article


Article 3

Small improvement to previous for old safari versions compatibility:​http://gist.github.com/gists/434145

View Article

Article 2

thanks jake, here's my (dirty) take on the override:​http://gist.github.com/431639 what would be a clean solution? probably adding an absolutely positioned element to an iframe, scrolling it and then...

View Article


Article 1

my workaround is $.browser.mobileSafari = /webkit.*mobile/i.test(navigator.userAgent) $.fn.cssKluge=function(css){ if ($.browser.mobileSafari){ css.top-=window.scrollY css.left-=window.scrollX }...

View Article

Article 0

+1 Same issue as reported in JQuery forum: ​http://forum.jquery.com/topic/offset-returns-incorrect-values-in-ipad

View Article

Browsing latest articles
Browse All 34 View Live




Latest Images