Last modified: 2012-04-19 15:49:48 UTC
I am using Wikipedia Mobile on a Blackberry Bold 9650, running Blackberry OS 6.0 bundle 3084. A couple of months ago, I noticed that the search bar at the top of my screen was reduced in height, with the result that only the top half of the search terms was visible. I lived with this, but yesterday the box shrank further, and now it is impossible to see any of the letters at all (except for very tall letters such as h and l, in which case the very tip of the vertical is visible). I can tell that the letters are being detected by Wikipedia, because I am getting search suggestions based on what I am typing. As you can imagine, it is very difficult to search when you cannot see what you are typing. This bug also exists in Opera Mini, but is not as severe because Opera requires you to enter the text into a dialog box before the field is populated, enabling you to see the letters before you press Enter. However, I dislike the Opera Mini browser and don't want to be forced to use it just because of this issue. I would really appreciate your help in getting this fixed.
Fixed in https://gerrit.wikimedia.org/r/5029 dundeepoet It would be really useful if you could test out our upcoming redesign of the mobile site for any bugs as we so far do a bad job on Blackberry testing! You can opt in by visiting http://bit.ly/woptin and leave via http://en.wikipedia.org/wiki/Special:MobileOptions/BetaOptOut Thanks for your assistance with highlighting this one!
Unfortunately, the bug does not seem to be fixed. I checked the site a couple of minutes ago (not using my old bookmark, but via a fresh Google search) and the problem is exactly the same as before.
Created attachment 10423 [details] Screenshot, Wiki mobile front page Screenshot of front page before entering any text
Created attachment 10424 [details] 2nd screenshot of Wiki mobile front page, with search term entered The word "Lycoperdon" is entered in the search box, but only the tops of the L and d verticals can be seen
It's currently only fixed in development. We have a deployment tonight so it should be visible tomorrow! Sorry for the confusion!!
Yes, I see it's fixed now. Many thanks.
*** Bug 35182 has been marked as a duplicate of this bug. ***
