Last modified: 2014-02-12 23:55:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T38383, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36383 - Potential problem with ICS 4.0.4 Samsung Galaxy Nexus Chrome Beta
Potential problem with ICS 4.0.4 Samsung Galaxy Nexus Chrome Beta
Status: RESOLVED INVALID
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Low normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-01 14:35 UTC by Jon
Modified: 2014-02-12 23:55 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jon 2012-05-01 14:35:05 UTC
Reported on the feedback page:
http://en.wikipedia.org/wiki/Wikipedia:Mobile_Extension_Feedback

There seems to be a major (unconfirmed) issue with the latest Chrome Beta and ICS.

########
Bring the old page back!

Or at least let people choose with which mobile page they'd rather go, because the new one is extremely bugged and looks terrible. (e.g. search does not work - Chrome Beta - Samsung Galaxy Nexus Android 4.0.4) 82.113.99.4 (talk) 14:02, 1 May 2012 (UTC)
User agent: Mozilla/5.0 (Linux; Android 4.0.4; Galaxy Nexus Build/IMM76I) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.133 Mobile Safari/535.19
Comment 1 Mark A. Hershberger 2012-05-01 17:10:47 UTC
(In reply to comment #0)
> There seems to be a major (unconfirmed) issue with the latest Chrome Beta and
> ICS.

Changing to unconfirmed.
Comment 2 Jon 2012-05-18 13:13:21 UTC
Does anyone have Chrome Beta on ICS and is able to replicate this? Otherwise I'll close since this is now several weeks old and was also reported on the dy of the update so could have been down to caching...
Comment 3 Jon 2012-05-21 09:45:20 UTC
Closing due to lack of activity and unconfirmed status

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links