On Wed, Jun 11, 2014 at 11:09 AM, Jon Robson <jdlrobson@gmail.com> wrote:
Hey Gautam thanks for sharing.

Hey! Not a problem at all.
 
So as I understand it really the issue here is not actually an Opera
issue but a resolution issue

True, and an extension of the problem is that devices in the smaller screen size ranges don't have browsers that support media-queries. Adding media queries will help Opera, but may not help others.

I think the decision to "support devices with small screens" has to be made by people measuring usage-per-browser, features-per-browser and market-expectancy-per-browser at Wikimedia. Once that decision is made, this one becomes easier.
 

There's a couple of issues here
1) The main page is a static page provided by the community -
https://meta.wikimedia.org/wiki/Www.wikimedia.org_template
Feel free to start a talk page comment about improving this for tiny
screens. This sadly is out of my control.

Understood
 

2) On all pages the content is mostly hidden because of the search,
watch star and menu icon. This is not helped by the fact Opera has
browser chrome on the top and bottom of the page - out of interest
Gautam, in the case of the device which is 320 by 240, what the
browser reports the width and the height of the window is (if we were
to use media queries and responsive design to adapt that).

You can use the media query max-device-width or max-width

Though in Opera's case, the screen width (240px) is the same the device width (240px). There is no chrome on the sides.
The height changes from 320px to 234px because of Opera's chrome, though users can choose to go fullscreen.
There is another Opera Mini client for smaller screen sizes which has a thinner chrome.

J2ME Low-end: Mini version 4.5 (thin chrome)
J2ME High-end: Mini version 8.0 (thick chrome)
Android: Mini version 7.5
iOS: Mini version 7.1
 

I actually think what would be the best solution here is to hide all
the Wikipedia chrome for screens, and replace it with links to Home
(and in future Search) at the top. I've knocked up a patch that does
this - https://gerrit.wikimedia.org/r/138867 and would be interested
in your views.

(will follow up on Adams reply on this)
 

On Tue, Jun 10, 2014 at 3:08 PM, Gautam Chandna <gautamc@opera.com> wrote:
> On Tue, Jun 10, 2014 at 2:46 PM, Adam Baso <abaso@wikimedia.org> wrote:
>>
>> I believe Gautam over at Opera may have some viewport stats he can share
>> with the list. He'll be emailing that pretty soon I think.
>
>
> I've just joined this mailing list, and have gone through this thread. I've
> got some data and screenshots that are relevant for this discussion:
>
> h3. Screen size for Opera Mini clients (sample data, 1 day):
> upto 400x320  50%
> 401x321 upto 470x320  3%
> 471x321 to 640x480  24%
> 641x481 to 960x720  17%
> 961x721 and above  7%
>
> I'm running this stat with lower screen sizes, for users using Wikipedia and
> will report here once I have new data.
>
> h3. Screenshots:
>
> Size 180 x 240, Size 240 x 320
> https://drive.google.com/folderview?id=0B-yck2WBt5TwekdHa0kxN0psRk0&usp=sharing
>
>
> This is what I presented yesterday at Wikimedia, to emphasize that there is
> a problem. Of course, you decide how to tackle it.
>
> Best regards,
> Gautam
>
>>
>>
>> I feel a compromise with a labeled "Add to Watchlist" button at the bottom
>> of the article on low-JS devices (freeing up the menubar at the top), but
>> keeping the star at the top on higher-JS devices (and hiding the "Add to
>> Watchlist" button at the bottom), is one way to strike a balance between
>> discoverability and usability in light of what seems to be pretty low
>> practical usage of the feature on the low-JS devices.
>>
>> -Adam
>>
>>
>> On Tue, Jun 10, 2014 at 12:43 PM, Juliusz Gonera <jgonera@wikimedia.org>
>> wrote:
>>>
>>> Federico Leva (Nemo) wrote:
>>>>
>>>> Juliusz Gonera, 10/06/2014 20:31:
>>>>>
>>>>> I would remove page actions for non-JS users if watchstar proves to be
>>>>> hardly ever used.
>>>>
>>>>
>>>> Personally I'm quite disturbed by the idea of further reducing
>>>> discoverability of editing/non-passive usage. I don't know about the
>>>> specific case, but remember not to trade the (visibility of the) *essence*
>>>> of the wiki for a few pixels saved.
>>>
>>>
>>> I understand this argument, however, on small feature phones with Opera
>>> Mini, the initial page view consists only of page header and a watchstar
>>> button. None of the article content fits without scrolling.
>>>
>>> --
>>> Juliusz
>>>
>>>
>>> _______________________________________________
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>>
>> _______________________________________________
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>
>
>
> --
> Gautam Chandna | Director - Technical Partner Management | gautamc@opera.com
> | +47-4567-1789
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>



--
Jon Robson
* http://jonrobson.me.uk
* https://www.facebook.com/jonrobson
* @rakugojon



--
Gautam Chandna | Director - Technical Partner Management | gautamc@opera.com | +47-4567-1789