Last modified: 2011-03-13 18:04:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 2090 - Main Wikipedia site is unreadable after final rendering on Treo 650
Main Wikipedia site is unreadable after final rendering on Treo 650
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
Other other
: Lowest normal with 2 votes (vote)
: ---
Assigned To: Hampton Catlin
:
: 4019 7217 (view as bug list)
Depends on:
Blocks: 1882
  Show dependency treegraph
 
Reported: 2005-05-06 17:45 UTC by Joshua Ochs
Modified: 2011-03-13 18:04 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Joshua Ochs 2005-05-06 17:45:37 UTC
Platform: Palm OS 5.4.5/Blazer 4.0/PalmOne Treo 650

Main Wikipedia site is unreadable (http://en.wikipedia.org/wiki/Main_Page_%28table_free%29). Prior to 
everything downloading (and thus, prior to final rendering) page displays as plain text with links and 
basic formatting ([http://homepage.mac.com/jochs/files/PreRendering-Wikipedia.jpg example]). After 
final rendering, the page is squashed into a thin vertical strip a few characters wide ([http://
homepage.mac.com/jochs/files/PostRendering-Wikipedia1.jpg one] and [http://homepage.mac.com/
jochs/files/PostRendering-Wikipedia2.jpg two]). This effect occurs with either "wide page" or "optimized" 
views. Same effect with the main front page, the "table free pages", and all article pages.

If the page loading is stopped midway, the original "non-rendered" version remains and is fully 
functional and readable. Timing when to stop the load (after content loads, but before the styling loads) 
is very difficult.

A completely plain version (similar to the "pre-rendered" version above) would be very useful, as it would 
be much more friendly to small screen sizes and slow connections.

I'll admit, I don't know if this is a basic Wikimedia bug or a Wikipedia specific one, so any corrections to 
how I have filed this are welcome.
Comment 1 JeLuF 2005-05-07 13:51:54 UTC
Is there any software emulator for the Treo 650 that we could use to reproduce
this bug?
Comment 2 Joshua Ochs 2005-05-07 18:32:58 UTC
I believe the Palm OS Simulator (http://www.palmos.com/dev/tools/simulator/) will do what you need. While I have not 
used it myself, I know a friend uses it for debugging his Palm-based VNC program.

As to whether or not it will have the proper version of Blazer, I have no idea.
Comment 3 Antoine "hashar" Musso (WMF) 2005-07-08 22:37:07 UTC
A possible fix is to use the mySkin skin (check your account preferences).
It comes with no formatting at all though you can add some by editing
your user stylesheet: user:Name/mySkin.css
Comment 4 Dysprosia 2005-11-18 01:47:09 UTC
*** Bug 4019 has been marked as a duplicate of this bug. ***
Comment 5 Dysprosia 2005-11-18 01:50:23 UTC
Perhaps Mediawiki or the servers (whoever's responsible) can either switch skins
or not load the stylesheet when it detects Blazer as the useragent? This is
*not* a Treo specific issue, but one with Blazer - I can confirm that my
LifeDrive which has Blazer 4 has the same problem as described above.
Comment 6 Alan Peterman 2007-05-09 17:34:01 UTC
I've had problems with my Palm T/x with Blazer 4.3 crashing on Wikipedia. 
Clearing the cache and the cookies seemed to solve it for a while.
Comment 7 Roger Stringer 2008-01-30 22:15:55 UTC
Confirm that the bad formatting issue exists with Treo 680 and Palm Centro devices.
A workaround is to go to Preferences in the Blazer web browser and set "Fast Mode" and set "Disable Cascading Style Sheets".
Comment 8 Nzinga 2008-04-30 00:52:52 UTC
I just switched my Centro's settings to "Fast Mode" and disabled the CSSs... still didn't work.
Comment 9 Chad H. 2008-12-13 02:15:08 UTC
*** Bug 7217 has been marked as a duplicate of this bug. ***
Comment 10 Brion Vibber 2008-12-15 20:12:53 UTC
Bump -- can anybody confirm whether our current handheld stylesheet changes this?
Comment 11 Chad H. 2008-12-15 20:44:08 UTC
As of a few days ago (can't get the Treo to connect to the internet today, it seems :(), still completely unusable. This is on a Treo 755p with Blazer 4.5.
Comment 12 Roger Stringer 2008-12-15 21:20:05 UTC
I just tried accessing from both a Palm Treo 650, Palm Treo 755p and a Palm Centro.  They have Blazer 4.5, though the 650's version is a trifle older.
I don't see any improvement.  Wikipedia is unusable on the Treo 650 and is only usable on the 755p and Centro if I configure "fast mode" with CSS disabled.

Comment 13 Brion Vibber 2008-12-15 21:26:37 UTC
Looks like I trimmed out the handheld style during an overload emergency and forgot to put it back.

Please test again. :)

Make sure you aren't getting a cached page, though... try
http://en.wikipedia.org/wiki/Special:Version
or similar
Comment 14 Roger Stringer 2008-12-15 21:40:28 UTC
Yes I can see (through Firefox) where you are defining the CSS for "handheld", but going to the Special: Version page doesn't change anything.
Comment 15 Hampton Catlin 2009-06-07 16:05:48 UTC
This ticket got assigned to me, but the Wikimedia-Mobile is only going to support
PalmPre unless someone wants to come up with a stylesheet that works on a phone
as old as that.

But, as far as my job, too many cell phone models to manage... and especially how
limited the generation being discussed here was.

I will happily accept a patch (stylesheet or otherwise), but please open another
ticket for that.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links