[TIMOB-15034] iOS7: WebViewControls - Unable to type anything into search bar and unable to search anything as well
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Not Our Bug |
Resolution Date | 2013-09-05T17:22:39.000+0000 |
Affected Version/s | Release 3.1.3 |
Fix Version/s | n/a |
Components | iOS |
Labels | ios7, qe-3.1.3, regression |
Reporter | Anshu Mittal |
Assignee | Vishal Duggal |
Created | 2013-09-04T11:05:20.000+0000 |
Updated | 2017-03-21T20:40:19.000+0000 |
Description
Unable to type anything into search bar and unable to search anything as well.
This is regression since the issue does not occur in 3.1.2 GA
Steps to reproduce:
1. Go to Kitchensink> BaseUI> Views> WebViews> Webview controls.
2. Type something into google search bar.
Expected:
User should be able to type into the search bar and search the content on the web.
Actual:
User is unable to type into search bar and search.
[~vduggal], thoughts?
My observations are as follows:
KS build with Xcode5DP6, with sdk 3.1.3.v20130904134612 on iphone4(IOS7):
1.Tapping on the google search bar first time shows the cursor at the right of the search bar & typing does not show us the letters being typed. 2.Tapping on the search bar second bar shows us the cursor on the left of the search bar & typing shows us the letters being typed.KS build with Xcode4.6.3, with sdk 3.1.3.v20130904134612 on iphone4(IOS6.0.1):
1.Tapping on the google search bar & shows us the letters being typed.KS build with Xcode5DP6, with sdk 3.1.2.GA on iphone4(IOS7):
1.Tapping on the google search bar first time shows the cursor at the right of the search bar & typing does not show us the letters being typed. 2.Tapping on the search bar second bar shows us the cursor on the left of the search bar & typing shows us the letters being typed.Its a typo, its tapping on the same search bar second time.
Since this a webview, only thing we do is load the webview, manage the back and forth stack and reload it. All other interactions within the webview itself is not in our control, at least in this case its a straight out google webpage and where the cursor appears on the webpage is completely up to the internal system and webpage itself.
Closing this ticket as the issue is not our bug.