I've got an app with a webview. It was working great, and then I moved the webView into an NSSplitView. Now it seems for some reason that whenever I press any key to enter text into the webview, it scrolls down. I haven't a clue as to what could cause this. Please help!
Figured it out... the webview was a pixel or so outside the bounds of the view it was inside of. I haven't any idea why that caused what it did, but when I put it back within the view's bounds, the problem went away. Weird.
Related
Sometimes in my UWP app I experience a problem while scrolling with my scrollwheel. Basically the scrollbar moves when I use my scrollwheel, but the content isn't rendered properly; resulting in an empty block which gets scrolled up and down.
Yet everything works fine when I click and hold the scrollbar instead of using the scrollwheel on my mouse.
I have to restart my UWP app in order to get things back to normal.
The issue appears while scrolling a default XAML ListView, but also in a RadDataGrid (Telerik).
I have made a screen recordingo of this issue, which hopefully will illustrate what's happening more clearly.
Click to see video
I haven't found exact steps to reproduce this issue, it just seems to be there at random from time to time.
Does anybody have an idea what might be going on here and how this could be fixed?
Here is the scenario. I'm developing an app for ipad. This app, is just a container for a web site. I created a webview that calls a website which has a textarea.
If I click inside this textarea and the softkeyboard is displayed, the view is pushed up more than the size of the keyboard. I fixed this by using the UIKeyboardWillShowNotification notification to put the view down again.
But check this. If I write inside the textarea, the view is pushed up again, even if is just one letter.
Here are some screenshots:
this is before writting something
this is after writting something
Has somebody had the same issue? Or any clue of what is hapenning?
Ok I figure it out. It was my fault, the cause was that the main view was a TableView. Changed to a simple View and everything is now perfect
I am using a UISwitch in one of my tabbed applications. The UISwitch is on the bottom of the screen. When I first start the App, the switch works fine. I can rotate from portrait to landscape, everything works fine. I can even go to other tabs and come back and the switch still works in both landscape and portrait. However, if I go back and forth between tabs maybe five times, the switch works in portrait, but not landscape . Has anyone ever seen or heard of this? Anyone know of a reason this could happen? I have used
[infoSwitch setOn:NO];
in my viewWillAppear, so that the switch always starts OFF. Is there something I am missing about using a switch? I did the same things I have done in the past to get switches to work. Any help will be much appreciated! Thanks again.
UIViews may be visible but will fail to get input if they're outside of the bounds of their parent view. So a first diagnostic would be to give the parent view some sort of obvious gaudy colour so that you can see its bounds visibly, then try your rotation and switching to see whether you can force an error there.
You can also set clipsToBounds to YES to ensure that views don't show subviews that are out of bounds.
In XCode, I have written an app which uses a UIScrollView with a background image. Up until this morning everything was working fine, but for some reason now, when I scroll the scroll view, the background image is scrolling twice the amount of the scroll.
Hope this makes sense to anyone, as I cannot figure out what I have done
OK. I've worked it out. I read a few other forums which had the same problem. I ended up adding a UIImage as a subview on my scroller, and set the image of that. It works fine now.
I suppose that may have been a bug up to 4.3 and now Apple have fixed it.
Ok, so I have a UIScrollView that contains several subviews, the subview I am having difficulties with is the UIWebView. When the webview is displayed on screen without having to scroll down the UIScrollView, everything works great (figure 1).
Where the problem starts is when the webview is loaded off the screen (figure 2), and scrolling is needed to view it (figure 3). The webview no longer responds to any user interaction.
I've tried some basic things like reloading the webview after the scrollViewDidEndDecelerating delegate is called, but nothing seemed to work. Has anyone encountered this before or have any suggestions on how to fix it?
Turns out this was working perfectly all along. Only problem was I had a wrapper UIView that contained the imageView and webview, but the wrapper wasn't getting resized, so touches outside its bounds weren't being respected. I just want to mention, a webview really shouldn't be placed in a scrollview. I'm only doing this because the webview is being sized according to its content and has scrolling disabled. Plus, there are currently no other views in the documentation that support links without heavy modification.