Last modified: 2014-02-21 00:03:59 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 T47955, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45955 - When we look at a page on the web mobile site of wikisource, we can't turn the page
When we look at a page on the web mobile site of wikisource, we can't turn th...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ProofreadPage (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: mobile
Depends on:
Blocks: Wikisource
  Show dependency treegraph
Reported: 2013-03-10 13:47 UTC by Zil
Modified: 2014-02-21 00:03 UTC (History)
12 users (show)

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

Wikisource mobile Chapter View (200.38 KB, image/png)
2013-03-10 13:47 UTC, Zil
Wikisource mobile Page View (178.46 KB, image/png)
2013-03-10 13:50 UTC, Zil

Description Zil 2013-03-10 13:47:52 UTC
Created attachment 11904 [details]
Wikisource mobile Chapter View

In Wikisource, we've got a page view like here :

On top of the page view we could go to the next page or previous page using the < or > buttons.

Those buttons are unavailable when you connect from a mobile to the mobile web site of wikisource. Making the reading of a book page by page really complex.

When we are in chapter view, we've got n option to go to the next chapter.

Dereckson point me to that extension, but we are not sure this is the one responsible.

I attached a chapter view and page view for esay references.
Comment 1 Zil 2013-03-10 13:50:10 UTC
Created attachment 11905 [details]
Wikisource mobile Page View
Comment 2 Andre Klapper 2013-03-11 16:18:16 UTC
Not sure about the best software component either - tentatively moving from ProofreadPage to MobileFrontend.
Comment 3 Tpt 2013-03-16 09:16:16 UTC
I believe it should be handle by Proofread Page as it's Proofread Page related features but as long as Mobile Frontend is not merged into core, it's more easy to add mobile related features into Mobile Frontend. than in other extensions.
Comment 4 Jon 2013-04-09 21:07:16 UTC
What needs to happen here is Proofread extension should add its own module to mobile that adds this feature. (alternatively if the javascript that does this is small you may want to test the code you've written on desktop and attempt to enable the same code you use on desktop)

We now have full RL support so it should be as simple as:

$wgResourceModules['mobile.proofreadpage'] = array(
	'scripts' => array(
	'position' => 'top',
'targets' => array( 'mobile' ), // or array( 'mobile', 'desktop' ) if you want to use same module
	'mobileTargets' => array( 'stable', 'beta', 'alpha' ),

MobileFrontend currently adds any modules that have been set to target mobile and set a mobileTargets

I'd suggest enabling it on the beta site of wikisource first and spend some time testing it before switching it on on stable.
This is as simple as setting:
'mobileTargets' => array( 'beta', 'alpha' ),

Word of warning: 
The mobile environment may be missing parts of the mw library so be careful what you use!

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