On the Blazer browser that comes standard with PalmOS 5
devices like the Treo 650, Slashdot renders with each
character on a separate line. This is unreadable.
Slashdot was perfectly readable on this browser before
the CSS transition. This happens both in Optimized mode
(reformats page to fit on the screen width wise), and
Wide mode (should render the same as a desktop browser).
Logged In: YES
user_id=289009
More information (different user):
I am running Blazer v4.3 as built into the new Palm TX with
built-in WiFi/Bluetooth. As mentioned, in both the Optimized
and Wide mode, Slashdot renders poorly.
The rendition problem is pretty much the same regardless of
[Simple Design] and [Low Bandwidth] settings (both or one
setting on and off].
It seems the page pretty much renders fine all the way up to
"The next Slashdot story will be ready soon, but subscribers
can beat the rush and see it early!"
Then, after that, all story titles and text and what not are
only a few character wide. EXAMPLE:
Amer
icans
Using
Inter
net
'Just
for
fun'
Posted
by Zonk
on 10:36
A<
Februar
y 16th,
2006
This continues all the way until the bottom section.
Everything is fine starting with the horizontal rule (which
is full screen width) and the "All trademarks and copyrights
on this page are owned..." Perfect all the way to the bottom.
Unfortunately, Slashdot is incredibly painful to read on the
Palm platform due to this rendering issue.
In case you care, my UserId is AtariDatacenter. Hello!
Logged In: YES
user_id=289009
UPDATE: Okay. Now I'm getting just as the submitted says.
Just one character wide for the central body of the page
("central body" as defined in my previous message). ALSO...
the page appears quite readable UNTIL it fully loads. I'm
guessing that is when it kicks in the CSS rules or something.
Logged In: YES
user_id=289009
Sorry. This'll be my last comment on this (unless asked a
question).
On Blazer, if I go into Options -> Preferences, and go to
the [GENERAL] tab, if I click on "Fast Mode", I can then
instruct it to Disable caascading style sheets.
Unfortunately, this is a global option. And it ends up
printing the side parts of the page at the top. But the
wrap-around misfeature is gone with CSS disabled, so it
looks to be some sort of CSS interpretation issue.