Hi,
On 24 May 2010 21:09, David Gerard dger...@gmail.com wrote:
On 24 May 2010 20:04, David Gerard dger...@gmail.com wrote:
Do we have a known graceful-degradation path when a browser is just
too crappy to deal with l33t skins like Vector? I'm thinking of the
PS3 users here, noisy as they
Maybe could be usefull to have a special url that automatically
disable vector, and make this setting continue with the session (is
that even possible?).
Like
http://en.wikipedia.com/classicview
So people designing smartphones, that want his smartphone to use the
old interface, can make the link
On Mon, May 24, 2010 at 7:48 AM, Tei oscar.vi...@gmail.com wrote:
Maybe could be usefull to have a special url that automatically
disable vector, and make this setting continue with the session (is
that even possible?).
http://en.wikipedia.org/wiki/?useskin=monobook
You have to readd
On 24 May 2010 16:25, Aryeh Gregor simetrical+wikil...@gmail.com wrote:
On Mon, May 24, 2010 at 7:48 AM, Tei oscar.vi...@gmail.com wrote:
Maybe could be usefull to have a special url that automatically
disable vector, and make this setting continue with the session (is
that even possible?).
On Mon, May 24, 2010 at 11:34 AM, David Gerard dger...@gmail.com wrote:
Is there any reason not to make useskin= persistent? i.e., to render
all internal links on a page with a useskin= if one was used in the
URL?
Yes. We'd have to either fragment the parser cache, or implement some
type of
On 24 May 2010 17:25, Aryeh Gregor simetrical+wikil...@gmail.com wrote:
On Mon, May 24, 2010 at 7:48 AM, Tei oscar.vi...@gmail.com wrote:
Maybe could be usefull to have a special url that automatically
disable vector, and make this setting continue with the session (is
that even possible?).
David Gerard wrote:
On 24 May 2010 16:25, Aryeh Gregor simetrical+wikil...@gmail.com wrote:
On Mon, May 24, 2010 at 7:48 AM, Tei oscar.vi...@gmail.com wrote:
Maybe could be usefull to have a special url that automatically
disable vector, and make this setting continue with the
On 24 May 2010 19:58, Naoko Komura nkom...@wikimedia.org wrote:
Another possible solution is to serve the mobile site when the page is
requested from blackberry. I am working with Tomasz and Hamton, if we
can make the switch.
That's the obvious answer, yes :-)
Do we have a known
On 24 May 2010 20:04, David Gerard dger...@gmail.com wrote:
Do we have a known graceful-degradation path when a browser is just
too crappy to deal with l33t skins like Vector? I'm thinking of the
PS3 users here, noisy as they are considering their near-negligible
user percentage. ('Cos when
vyznev wrote:
I'd suspect some script is trying to do an API query using a very long URL,
and the fact that this only happens when JS is enabled lends support to
this.
I don't see any long url requested on enwiki.
I would guess that the Javascript associated with Vector is using more
On 14 May 2010 16:34, Platonides platoni...@gmail.com wrote:
vyznev wrote:
I'd suspect some script is trying to do an API query using a very long URL,
and the fact that this only happens when JS is enabled lends support to
this.
I don't see any long url requested on enwiki.
I would guess
On Fri, May 14, 2010 at 10:51 AM, Tei oscar.vi...@gmail.com wrote:
Maybe a Blackberry emulator can be usefull (one that is accurate). Any
idea of where one can be downloaded?
First google result:
http://na.blackberry.com/eng/developers/resources/simulators.jsp
-Chad
BTW, Vector is also breaking the PS3 browser, according to a couple of
comments on the blog post.
We seem not to be quite achieving that graceful degradation thing
immaculately ...
- d.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
When visiting a vector site with a Nokia N-series (tested on N90,95and
96) viewing it on Opera Mini there are problems also.
Its impossible to click the buttons userpage, talkpage, watchlist ..
they are all in the same spot, trying to press will give the
prefences.
The Buttons with Edit Talk
There's a few comments on the Wikimedia blog saying they can't access
en:wp any more using their BlackBerry. Though we tried it here on an
8900 and it works. Any other reports?
- d.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Thu, May 13, 2010 at 3:16 PM, David Gerard dger...@gmail.com wrote:
There's a few comments on the Wikimedia blog saying they can't access
en:wp any more using their BlackBerry. Though we tried it here on an
8900 and it works. Any other reports?
Punching in http://en.wikipedia.org/ as I
David Gerard dger...@gmail.com wrote in message
news:aanlktin9qhcgvataegsdrwjuc-jegj-iwdg6f9oyt...@mail.gmail.com...
There's a few comments on the Wikimedia blog saying they can't access
en:wp any more using their BlackBerry. Though we tried it here on an
8900 and it works. Any other reports?
On 05/13/2010 10:55 PM, Russell Blau wrote:
David Gerarddger...@gmail.com wrote in message
news:aanlktin9qhcgvataegsdrwjuc-jegj-iwdg6f9oyt...@mail.gmail.com...
There's a few comments on the Wikimedia blog saying they can't access
en:wp any more using their BlackBerry. Though we tried it here
2010/5/13 Ilmari Karonen nos...@vyznev.net:
Error 413 generally means, in plain English, URL too long. I'd
suspect some script is trying to do an API query using a very long URL,
and the fact that this only happens when JS is enabled lends support to
this.
Assuming that the Blackberry
On Thu, May 13, 2010 at 1:39 PM, Roan Kattouw roan.katt...@gmail.com wrote:
2010/5/13 Ilmari Karonen nos...@vyznev.net:
Error 413 generally means, in plain English, URL too long. I'd
suspect some script is trying to do an API query using a very long URL,
and the fact that this only happens
20 matches
Mail list logo
