Opened 9 years ago

Closed 9 years ago

#7234 closed bug (wontfix)

iPad Safari truncates tab content on lengthy documents

Reported by: tr888 Owned by:
Priority: minor Milestone: 1.9.0
Component: ui.tabs Version: 1.8.11
Keywords: Cc:
Blocked by: Blocking:

Description

My website uses jQuery UI Tabs to organize some fairly large documents (e.g. 75K) into sections, each of which has a corresponding tab. The pages work fine EVERYWHERE (Opera, Chrome, FF, IE, Safari for Windows, Safari for Mac) but not on iPad Safari, where the tab-content is getting truncated. The pages validate as 4.01 Strict.

I have a jsFiddle project demonstrating the problem: http://jsfiddle.net/Ybmk9/8/

The [Glossary] tab's contents should go all the way down to the letter -Y- but it cuts off in the letter -H- on the iPad.

It is as though iPad Safari is "remembering" the tab pane height from a "shorter" DIV and applying that height to the DIV that is being made visible, even if the DIV-to-be-made-visible is lengthier than the previous one and should have greater height.

Here is my actual website: www.aimsdata.com/tim/anhaga/edition.htm

Change History (5)

comment:1 Changed 9 years ago by tr888

Version tested on jsFiddle is 1.8.9 -- don't see how to edit the version here, which reads 1.8.11. Sorry

comment:2 Changed 9 years ago by tr888

This means my site is pretty much useless on iPad, a platform I'd really like to target; my site is text-centric and scholastic/academic oriented. So I'd like to consider this worse than a "minor" bug but I don't see how to change the priority to "major". I don't understand the bug-reporting interface; for example, why is there a radio-button (*) "leave as new" under Modify Ticket? Aren't single-choice options usually represented by a check-box, with radio-buttons being reserved for multiple mutually exclusive options?

comment:3 Changed 9 years ago by tr888

I tested today at the Apple store on the iPad2 and the page works fine. This isn't to say that it might not stop working on the iPad2 at some point, if, say, it were a caching issue. But I believe this isn't a jQuery bug but an Apple issue.

comment:4 Changed 9 years ago by etiger13

I tried this on my ipad and it only shows in the example window. If you use http://jsfiddle.net/Ybmk9/8/show/ it works fine.

comment:5 Changed 9 years ago by Scott González

Resolution: wontfix
Status: newclosed

Closing as it sounds like all the research is showing that this is a limitation that only occurs in iframes that can't be worked around and is fixed in newer versions.

Note: See TracTickets for help on using tickets.