Hi,
Often mobile tickets need more knowledge of mobile and awareness of
the state of things than I can offer. And they often are neglected in
tech-issues. (I think more than other kinds of tech issues?)
Are you interested in only MobileFrontend issues or also
Vector/Monobook on mobile devices?
Options:
* we could forward stuff to mobile-l (sometimes without even bothering
to search bugzilla)
* we could get a template like we already have for wikitech-l
referrals to tell people they should be mailing mobile-l instead
* maybe we could get mobile people paying attention to OTRS?
(especially because you're already using OTRS for the apps. speaking
of apps, do you reply to those tickets at all? I sent a few in myself)
-Jeremy
Hello Jeremy!
For me, that seems to be normal for desktop sites on mobile devices (that's one of the plusses to use MobileFrontend :P). For example see the Nexus 7 Screenshots from Wikipedia and another website (on the other website you see the difference between the "normal" font size (very little and blurry) and a bigger font (better to read)). If you zoom the site in the browser, the font is much clearer and bigger, so better to read, so on Android tablet, I think on iPad, too.
Wikipedia Nexus 7: http://i.imgur.com/Iaf8SvK.png Other website Nexus 7: http://i.imgur.com/miUxm2O.png
Normally the user will be automatically redirected to the Mobile optimized site (MobileFrontend) with an iPad, so, if he want to see the desktop site, he must opt-out with the link at the bottom.
P.S.: Sorry Jeremy for sent this mail twice, in first mobile-l wasn't added :)
Kind regards
Florian
Freundliche Grüße
Florian
-----Ursprüngliche Nachricht-----
Von: mobile-l-bounces(a)lists.wikimedia.org [mailto:mobile-l-bounces@lists.wikimedia.org] Im Auftrag von Jeremy Baron
Gesendet: Sonntag, 29. Juni 2014 03:13
An: mobile-l
Betreff: [WikimediaMobile] Fwd: Blurry text on iPad
Hi,
(see also my other mail just now on mobile non-app feedback in general)
In this case I searched bugzilla for ~5 mins and didn't see anything relevant and so I forward here. Although, maybe I used the wrong search keywords. (quicksearches were ":mobilefrontend summary:text", ":mobilefrontend summary:font" and ":mobilefrontend blur". and then I realized of course this isn't MobileFrontend at all and tried again with "ipad|ios font|text|blur") I don't see the issue myself but I'm not looking on an iPad. It may be valid or WORKSFORME or fixed but not yet deployed.
At first glance this seems like Brion's kind of bug?
I just asked the user about the rendering with MobileFrontend. (I guess they must have opted out because it's such recent feedback?
given the recent switch to redirect tablets also by default.)
-Jeremy
(obviously removed name and redacted screenshot a bit)
screenshot now uploaded instead of attached because list has a size limit:
https://i.imgur.com/oLFawll.png
---------- Forwarded message ----------
From: OTRS 2014062710022031
Date: Fri, Jun 27, 2014 23:00 UTC
Subject: Blurry text on iPad
To: "info-en(a)wikimedia.org" <info-en(a)wikimedia.org>
Just to report a bug - Since today, the text became blurry on the main content area of the site while visiting wikipedia on a non-retina iPad in portrait orientation (the top and sidebar remains sharp). You can find a screenshot in attachment. This also happens while visiting articles.
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
There are three important bugs that need to be fixed in VE before we can
move it to stable for tablets (specifically iPads). The first two were
added by me just today. The third was reported in May by Rummana and for
some odd reason had Jon assigned to it, although he has never worked on it
(I removed him).
Following Roan's suggestion I recorded videos on iOS simulator to
illustrate what is happening in each case (thanks to Monte for letting me
use his Macbook with up-to-date Xcode).
https://bugzilla.wikimedia.org/show_bug.cgi?id=66999https://bugzilla.wikimedia.org/show_bug.cgi?id=67002https://bugzilla.wikimedia.org/show_bug.cgi?id=65326
Let us (the mobile team) know if you need any help with those.
--
Juliusz
I was going to resubmit the patch below by updating the W0 and sidebar
verbiage, but I noticed the word "article" is used in lots of other places.
Okay if I make the changes in the other places for the actual string values
on the righthand side of the = operator? I don't really care to touch the
lefthand side keys of the messages at this point.
-Adam
On Wed, Jun 25, 2014 at 7:05 AM, Siebrand (Code Review) <
gerrit(a)wikimedia.org> wrote:
> Siebrand has posted comments on this change.
>
> Change subject: Update W0 flourishes based on UX feedback for MVP.
> ......................................................................
>
>
> Patch Set 1:
>
> (1 comment)
>
>
> https://gerrit.wikimedia.org/r/#/c/141852/1/wikipedia/en.lproj/Localizable.…
> File wikipedia/en.lproj/Localizable.strings:
>
> Line 16: "zero-charged-verbiage-extended" = "Loading other articles may
> incur data charges. Saved articles stored offline do not use data and are
> free.";
> > Currently, the app sidebar says "Saved articles". Should the sidebar say
> "S
> Yes, please use page consistently.
Today's update to the Alpha and Beta[1] versions of the Android app
includes the following changes:
- Added option to refresh Saved Pages.
- Improved styling of Login and Create Account screens.
- Improved handling of Random pages.
- Updated translations/internationalization.
- Numerous bug/crash fixes.
We're getting very close to the production 2.0 release. So, please continue
to put the app through its paces! We want as much of your valuable
feedback as possible.
Bernd
[1]: https://play.google.com/store/apps/details?id=org.wikipedia.beta
Hi everyone,
We just met with Lila to show her the app. In short, she approves! Full
speed ahead! :-)
I took some notes on the things she was suggesting in the meeting. Here
they are: http://etherpad.wikimedia.org/p/LilaAppNotes
We'll work these into the backlog. For now, we all know what we've got to
do!
Thanks,
Dan
--
Dan Garry
Associate Product Manager for Platform and Mobile Apps
Wikimedia Foundation
Hi everyone,
So that the Communications team has a baseline which they can operate from,
we've set a specific time at which the APK for the Android release will be
pushed to the store. We'd already agreed on the date, 25th June, but now
we've set a specific time: 9am (SF time) on Wednesday 25th June.
The Communications team is aware that, in order to be fully accessible, the
app must still then propagate through Google's servers and that we have no
way of knowing how long this will take. But guaranteeing that we will at
least push the APK at a set time removes one of the variables from the
equation for them.
Thanks!
Dan
--
Dan Garry
Associate Product Manager for Platform and Mobile Apps
Wikimedia Foundation
Hi,
In the MobileFrontend test suite is a build that targets the production
English Wikipedia. On several occasions over the last few months rogue
tests from that build have created test pages in production.
This happened again yesterday, and as a result, I removed en.m.wikipedia.org
from all the Mobile browser tests [1] and Zeljko has deleted the
MobileFrontend build that targets production completely, so this should not
happen again.
However, as of this morning and because of these test pages, the
Selenium_user is blocked indefinitely on English Wikipedia [2].
I am inclined to continue to have Selenium_user blocked in production, I
think it is a good idea.
If you have any reason to use the Selenium_user in production, please let
me know in the next twenty four hours or so.
Thanks,
-Chris
[1] https://gerrit.wikimedia.org/r/#/c/141463/
[2] https://en.wikipedia.org/wiki/User_talk:Selenium_user#June_2014
