Aren't most mobile browsers supposed to be redirected to mobile.wikipedia.org anyway? BTW, we are slowly fixing Vector issues for obscure browsers. For example, I just recently fixed Vector for the PS3's browser. To fix these issues we need 2 things: A complete description of the environment and display behavior (preferably with a screenshot or even a photo of your cell phone screen), and a way to test it. For some mobile phones we can use emulators, but for others we have no easy way to test Vector on them. Ryan Kaldari On 8/17/10 1:20 PM, Magnus Manske wrote:

On 8/17/10 2:33 PM, David Gerard wrote: I'm not sure insulting the people who worked on Vector is the best way to motivated them to fix things. At the last company I worked for (which owns a couple of top 100 websites and has a staff of thousands), they didn't even care about their sites working right on iPhones. Considering the number of cell phones that Vector does work on, and the fact that it was implemented by a small handful of developers, I think they should be commended rather than insulted. But that's just me. (FYI, I had no involvement in Vector development.) This is a useful suggestion and I'll see if it's doable. Ryan Kaldari

I just looked and I could only find 2 bugs filed about Vector not working on mobile devices. The first was for it being broken in NetFront browsers. This was fixed less than a month after being reported (and within a week of Wikimedia getting a device to test on). The second was for Vector crashing some blackberry phones. This was traced to a bug on Blackberry's side (the same day the bug was reported). A work-around was implemented a week later. Further testing was done on eight different models of blackberries and across 3 different Firmware versions. It was determined that phones upgraded to the v5 Firmware no longer crashed. That doesn't sound like Wikimedia being "slow to act". And for what it's worth, Vector was apparently tested on IEMobile. It worked in the tests, but of course it's impossible to test every version of every browser on every phone OS. Thanks for sending the user agent string, that will be useful for filing a bug in Bugzilla. Ryan Kaldari On 8/18/10 12:10 PM, David Gerard wrote:

I think you guys are experiencing the java-script load issues, Due to our amount of javascript that is loaded some browsers (eg: IE6 on desktop) can't handle it and refuses to load and errors out, This <s>should</s> will be fixed when the work on the resource loader branch is finished and merged.

On Thu, Aug 19, 2010 at 11:52 AM, 49342) &lt;mah(a)everybody.org&gt; wrote: Forget memory -- the extra network and processing time involved in fetching an extra complete HTML+CSS+JS version of the page, then throwing it away and fetching another one, is wasteful and annoying even on highly capable phones! However, we can't just use a User-Agent check in PHP for this, since 90-something percent of the time the PHP scripts are not being executed: the Squid caches respond to most web requests directly. So what would be required would be some filtering in the caches to check for particular User-Agents or other settings and send them the redirect directly, or send them through to PHP for possible redirection. (Assuming there's no problem with downstream caching, which I think should usually be ok the way we have things marked -- as long as the redirect responses are marked as private-cache or uncacheable.) A JavaScript hack was quicker to put in place than the cache-level logic, but it was only ever meant as a stopgap. -- brion vibber (brion @ pobox.com)

yup, its seem fairly doable and the issue has been raised to our ops team. we're waiting to hear back about what's necessary in order to make it work. --tomasz On Aug 20, 2010, at 3:59 PM, Platonides wrote:

On Wed, Aug 18, 2010 at 3:29 PM, David Gerard &lt;dgerard(a)gmail.com&gt; wrote: I think they mean that when they Google something, it gives them a link to the article on en.wikipedia.org, not the mobile site. You should probably tell them not to worry and that they'll automatically be redirected to the article on the mobile version (m.en.wikipedia.org). -- Casey Brown Cbrown1023

On 19 August 2010 02:19, Ryan Kaldari &lt;rkaldari(a)wikimedia.org&gt; wrote: That appears to have been the problem with older BlackBerrys, i.e. the browser just ran out of heap. - d.