Load any page with image assets. Scroll the window so that the image overlaps the search input box. Tap the search input box. You'll get an image detail page instead of the search input box.
Version: 1.0.0 (Android)
Severity: normal
Load any page with image assets. Scroll the window so that the image overlaps the search input box. Tap the search input box. You'll get an image detail page instead of the search input box.
Version: 1.0.0 (Android)
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T33702 Android app shows blank screen after network failure | |||
| Resolved | • Tfinc | T33447 Android App 1.0 release (tracking) | |||
| Declined | None | T34917 It's difficult to tap into the search box | |||
| Resolved | yuvipanda | T34319 Android app doesn't allow search when webview overlaps with an image |
herman.wong wrote:
hmmm. tried using event.stopPropagation on the search field (searchParam input)
and on the search bar (mainHeader div) but the click/touch event still
activates on the image underneath the search area.
herman.wong wrote:
https://github.com/nitobi/Wikipedia/commit/d92b124b28f162746fba3ba8c8de37887cfa3c32
seems to do the fix this issue, but has a slight side effect where the keyboard hides after the 1st character is typed...
updated link from last comment:
https://github.com/Wikimedia/WikipediaMobile/commit/d92b124b28f162746fba3ba8c8de37887cfa3c32
This seems to be (mostly?) resolved by this bit in android/platform.js's onDeviceReady:
// this disables the "click-through" of an image under the search bar - but hides the keyboard only on the first character typed...
$('#searchParam').bind('touchstart', function () {
$('#searchParam').focus();
plugins.SoftKeyBoard.show();
return false;
} );However, that appears to be the cause of bug (mumble muble -- there appear to be at least two of them) -- with the focus ring / cursor not appearing on their own when tapping into the search bar.
We have some related issues with the 'W' and search icons -- is there a separate bug for em we can't find? :)