Last modified: 2014-02-12 23:55:24 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 T55738, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53738 - Particular section fails to expand
Particular section fails to expand
Status: RESOLVED WORKSFORME
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-04 07:37 UTC by king.of.hearts.wiki
Modified: 2014-02-12 23:55 UTC (History)
10 users (show)

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


Attachments

Description king.of.hearts.wiki 2013-09-04 07:37:04 UTC
I am forwarding a bug report from OTRS #2013083010016718 here. Apparently, when you try to access the article "Charles, Prince of Wales" on the English Wikipedia on mobile, and you try to expand the "Ancestry" section, nothing shows up.

I have been able to reproduce this bug using an iPhone 4 running iOS 6.1.3, on both the mobile website and the Wikipedia app. However, the mobile website version of the same article works perfectly fine on my Windows PC, whereupon "Ancestry" expands to show the whole thing.

I did not ask him what phone he was using.
Comment 1 Brion Vibber 2013-10-30 15:39:21 UTC
Old app's being retired and reimplemented, but this seems to be a problem with the MobileFrontend styles as combined with that particular page. Reassigning to MobileFrontend.
Comment 2 Bingle 2013-10-30 15:40:19 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1343
Comment 3 Jon 2013-10-30 16:14:18 UTC
Since you can expand this section now (on the iOS device in question) I assume the problem has gone away. Please reopen if you see this again somewhere.

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


Navigation
Links