[TIMOB-5907] iOS - Disable shadow on webView
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2020-02-14T09:28:45.000+0000 |
| Affected Version/s | Release 1.7.3 |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | n/a |
| Reporter | Sindre Sorhus |
| Assignee | Rene Pot |
| Created | 2011-10-29T15:40:38.000+0000 |
| Updated | 2020-02-14T09:28:45.000+0000 |
Description
Let say you need some advanced styling for your content, so you decide to use a webView. The downside with this besides the high memory use, is that the webView has shadows on the top when you drag your content down, so it's obvious that it's an webView.
!skitched-20111030-013938.png!
There should be a way to disable this shadow. Like an property on webView called
webView.shadow = false.
You can just follow [this answer](http://stackoverflow.com/questions/1074320/remove-uiwebview-shadow/3521263#3521263) on StackOverflow.
Attachments
| File | Date | Size |
|---|---|---|
| skitched-20111030-013938.png | 2011-10-29T15:40:38.000+0000 | 71152 |
I found this in Q&A and it seems to work: http://developer.appcelerator.com/question/118810/how-to-disable-scrolling-and-shadows-in-a-webview#answer-233259 It would be nice if it was included in the SDK though.
This is an important feature to help people to create native looking web apps. Without this you can't really use the webView without it being obvious that it's a webView... There's an easy 3-liner fix linked to from the issue. I've been waiting for this one for a long time. Hopefully someone can take a look at this.
bump
Still present...Please just add the following code to the core (TiUIWebView.m): -(void)setHideShadow_:(id)arg { for(UIView *wview in [[[webview subviews] objectAtIndex:0] subviews]) { if([wview isKindOfClass:[UIImageView class]]) { wview.hidden = [TiUtils boolValue:arg]; } } }
can we just make this a PR already? Hans already pasted the code to do this.
This is not an issue anymore. Probably since iOS 7 or otherwise a PR fixed it in the meantime.