Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are a few ways of finding the height of a <code>UIWebView</code>'s content.</p> <p>Here are a few pointers to start with:</p> <p><a href="https://stackoverflow.com/questions/745160/how-to-determine-uiwebview-height-based-on-content-within-a-variable-height-uit">How to determine UIWebView height based on content, within a variable height UITableView?</a></p> <p><a href="https://stackoverflow.com/questions/3936041/how-to-determine-the-content-size-of-a-uiwebview">How to determine the content size of a UIWebView?</a></p> <p><a href="https://stackoverflow.com/questions/10299023/iphone-get-the-content-size-of-uiwebview">iPhone - get the Content Size of UIWebView</a></p> <p>Note that using a <code>UIWebView</code> in a <code>UITableView</code> isn't necessarily a very good idea, specially if you have many <code>Announcements</code> to scroll through in the same <code>UITableView</code>. If you show only one Announcement per <code>UITableView</code>, you should be able to get away with it, but for tables with a lot of cells to scroll through, using webviews in the cells can lead to bad performance issues.</p> <p>Apple also recommend against using embedding <code>UIWebViews</code> / <code>UITableViews</code> / <code>UIScrollViews</code>.</p> <p>From the <a href="http://developer.apple.com/library/ios/#documentation/uikit/reference/UIWebView_Class/Reference/Reference.html" rel="nofollow noreferrer">UIWebView Class Reference</a> : </p> <blockquote> <p><strong>Important</strong>: You should not embed UIWebView or UITableView objects in UIScrollView objects. If you do so, unexpected behavior can result because touch events for the two objects can be mixed up and wrongly handled.</p> </blockquote> <p>My 2 cents :)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload