Last modified: 2012-10-21 19:21:06 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 T34597, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32597 - MobileFrontend should provide a way for the pages to display mobile-only content
MobileFrontend should provide a way for the pages to display mobile-only content
Status: RESOLVED WONTFIX
Product: Wikimedia Mobile
Classification: Unclassified
Generic (Other open bugs)
--
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Tomasz Finc
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-22 21:51 UTC by Strainu
Modified: 2012-10-21 19:21 UTC (History)
2 users (show)

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


Attachments

Description Strainu 2011-11-22 21:51:39 UTC
When we activated the old mobile homepage on ro.wp, we decided to provide a stripped-down version of the quality articles, as well as some other sections.

With the new id system, this is not possible, since we don't know when the mobile site is active. I thought about introducing an invisible div for the mobile site, but that is an ugly hack. THere should be a way of deciding whether a certain page is served for the mobile site or for the main one.
Comment 1 Jon 2012-10-19 19:17:15 UTC
It's not clear what needs to be done here.

Pages that render incorrectly on mobile should be dealt with on a case by case basis. If a user is viewing the mobile site every page should be mobile optimised as otherwise the experience is just confusing (with the complete change of UI)

Note you can wrap desktop content in a class nomobile to remove it from the mobile output.
Comment 2 Strainu 2012-10-21 19:21:06 UTC
What needs to be done here is to also have a class mobile (since we have class nomobile). I am not reopening this since class nomobile works for my usecase.

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


Navigation
Links