Closed Bug 570323 Opened 10 years ago Closed 9 years ago

Use m.wikipedia.org for Wikipedia searchplugin

Categories

(Firefox for Android Graveyard :: General, defect, minor)

defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: toniher, Assigned: mbrubeck)

Details

(Keywords: polish, productization, Whiteboard: [has-patch])

Attachments

(1 file)

m.wikipedia.org is a mobile light version of Wikipedia (also available in several languages). This is quite convenient when searching in unstable connections and low bandwidth (considering also paying per time). Shouldn't we switch current Wikipedia searchplugin to a m.wikipedia.org version?
I'm torn. On one hand, I like the idea of having the 'real', full-featured Web in my Fennec. No compromises, just the real thing.

On the other hand, the default Wikipedia skin really is hard to read on a 3- or 4-inch device. The mobile version focuses on the content while hiding tools like history, discussions, other languages etc. Most of them are not crucial while browsing on a mobile device, probably, although I personally do miss 'other languages'. I tend to use Wikipedia as a dictionary a lot.

On the plus side, there are two easily accessible links at the bottom of every page in mobile Wikipedia: "view this page in regular Wikipedia" and "permanently disable mobile Wikipedia". The second one doesn't seem to work atm (I'm getting an error: "Invalid target"), but if it did, that would be a cool feature.

Also, mobile Wikipedia doesn't currently offer a search plugin. I think they should start doing that if we were to ship with them.

To sum up, mobile Wikipedia is pleasure to read on a handheld device and I think that it might be a good choice for the default Wikipedia plugin shipped with Fennec. It also gives you a trivial way of going to regular Wikipedia from where a user like me can install the regular search plugin if they need the additional features (like 'other languages').

CC'ing other folks for their feedback.
Keywords: productization
(In reply to comment #1)
> I'm torn. On one hand, I like the idea of having the 'real', full-featured Web
> in my Fennec. No compromises, just the real thing.

I agree with everything you said, except the feeling that using the mobile site is not the full-web. Just because a webpage has a better layout for a mobile screen does not diminish its "fullness" IMO.

I'd be happy to switch the search plugin.
(In reply to comment #2)
> (In reply to comment #1)
> > I'm torn. On one hand, I like the idea of having the 'real', full-featured Web
> > in my Fennec. No compromises, just the real thing.
> 
> I agree with everything you said, except the feeling that using the mobile site
> is not the full-web. Just because a webpage has a better layout for a mobile
> screen does not diminish its "fullness" IMO.

I agree with Mark.
Assignee: nobody → mbrubeck
Keywords: polish
Version: 1.9.2 Branch → Trunk
Attached patch patchSplinter Review
This decision is somewhat out of our hands, since Wikipedia now redirects Firefox for Android to the mobile site regardless.  This patch will make Fennec go straight to the mobile site on all platforms.
Attachment #503645 - Flags: review?(mark.finkle)
Whiteboard: [has-patch]
Comment on attachment 503645 [details] [diff] [review]
patch

agreed
Attachment #503645 - Flags: review?(mark.finkle) → review+
http://hg.mozilla.org/mobile-browser/rev/2bed379363b2
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified as fixed on:
Mozilla /5.0 (Maemo;Linux armv7l;rv:2.0b10pre)Gecko/20110114 Firefox/4.0b10pre Fennec /4.0b4pre  
and 
Mozilla /5.0 (Android;Linux armv7l;rv:2.0b10pre) Gecko/20110114 Firefox/4.0b10pre Fennec /4.0b4pre
Good to see us moving forward with the decision making here, but I wish there'd been a heads-up given to the l10n drivers team about this landing.  This change will need to propagate to all other locales, and it won't take care of itself automatically during the build process because we use separate xml files for each locale for this search plug-in.  In the future, please consider keeping us in the loop before you land so that we can plan ahead our communication with and the workload for the localizers.  Thanks!
Stas - the main reason I r+ the patch was that wikipedia is already redirecting Fennec to the mobile page. Changing the searchplugin just saves some time during the redirect.

Any other locales using wikipedia are probably also being redirected, so l10n really could do nothing and the result would be the same. Any locale that gets time to update would result in the same "skip a redirect" that happens in en-US now.

That said, I don't mind being reminded that some changes need to include l10n - I do forget often. Thanks for keeping on top of things.
(In reply to comment #9)
> Stas - the main reason I r+ the patch was that wikipedia is already redirecting
> Fennec to the mobile page. Changing the searchplugin just saves some time
> during the redirect.

I agree with the r+ and I do agree that this is a good change.  I would have just preferred there'd been more time left between the r+ and the landing, so that we can plan how to talk to the localizers about this.  With our policy of requiring localizers to file bugs and ask for review for any changes to localized search plugins, a landing like this can cause some confusion and result in a flurry of bugs that we then have to handle :)

For this particular case, I think we'll ask the localizers in the newsgroups to commit the change without going through bugzilla, to save us some trouble.

> Any other locales using wikipedia are probably also being redirected, so l10n
> really could do nothing and the result would be the same. Any locale that gets
> time to update would result in the same "skip a redirect" that happens in en-US
> now.

That's a good point, thanks for bringing it up. It does seem like the landing had smaller impact that I thought it had.

> That said, I don't mind being reminded that some changes need to include l10n -
> I do forget often. Thanks for keeping on top of things.

Thanks as well!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.