[TIMOB-7519] TiAPI: Ti.UI.Webview showScrollbars property
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Won't Do |
Resolution Date | 2020-01-09T19:48:04.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | n/a |
Labels | parity |
Reporter | Chris Barber |
Assignee | Eric Merriman |
Created | 2012-02-02T11:08:21.000+0000 |
Updated | 2020-01-09T19:48:04.000+0000 |
Description
Added a showScrollbars property to Ti.UI.WebView for mobile web.
Data Type: boolean
Default Value: true
Controls the display both horizontal and vertical scrollbars. There is no mechanism for controlling a specific axis.
When true, show scrollbars in the WebView if the content is larger than the WebView.
When false, do not show the scrollbars, even if the content is larger than the WebView.
According to http://stackoverflow.com/questions/849225/iphone-is-it-possible-to-hide-native-scrollbar-in-uiwebview , we can hide/show scrollbar in iOS uiwebview like this: [(UIScrollView*)[webview.subviews objectAtIndex:0] setShowsHorizontalScrollIndicator:NO]; [(UIScrollView*)[webview.subviews objectAtIndex:0] setShowsVerticalScrollIndicator:NO]; this code works in iOS 4.0 - 5.0, but not in iOS 3.1.3. In iOS 4.0-5.0 [webview.subviews objectAtIndex:0] returns instance of _UIWebViewScrollView, which can be casted to UIScrollView, but in iOS 3.1.3 it returns instance of UIScroller, which failed to cast to UIScrollView. According to http://stackoverflow.com/questions/3998916/android-webview-leaves-space-for-scrollbar , we can hide /show scrollbar in Android webview like this: webView.setScrollBarStyle(View.SCROLLBARS_INSIDE_OVERLAY);
is it planned to add this to android/ios? would be nice to disable the scrollviews. I've disabled scrolling and touch but it still displays the scrollbars for a second when the webview is created. Hiding them would help
It has been decided that this issue should be closed as “Won’t do.” This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.