Re^3: A call to keyboards: Better chatterbox wrapping

Cool idea, but your CSS on your demo site does not work with Mozilla 1.1 - no scrollbars are shown, so all the text that does not fit into the one line allotted to it just vanishes...

It works in Firefox 0.9 and Mozilla 1.7. As an upgrade is available and free, I don't think a browser bug is a good reason for not doing this. And if a workaround is needed, try adding width and/or max-width CSS attributes. If the bug is that it no longer grows vertically, height: auto; might fix it.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

Comment on Re^3: A call to keyboards: Better chatterbox wrapping

Replies are listed 'Best First'.
Re^4: A call to keyboards: Better chatterbox wrapping by demerphq (Chancellor) on Jan 10, 2005 at 14:21 UTC
We have a definite requirement to support devices with weak and/or non-existant CSS support. While your idea is good, it doesn't address that requirement. Unfortunately not all of our users are using devices or in situations where upgrading or changing browsers is feasable so we need to find alternate solutions. --- demerphq	[reply]
Re^5: A call to keyboards: Better chatterbox wrapping by Juerd (Abbot) on Jan 10, 2005 at 14:26 UTC
What's the real problem when you're not wrapping? The side bar grows. Which devices use browsers that do not support CSS? I think most of them are devices with small screens, that can't render silly table based layouts correctly anyway. Others may be ancient browsers or text based browsers, but users who pick those are used to horizontal scrolling anyway, as table rendering improved much in the past few years. I'm curious which specific supported user agent has a screen big enough to handle the big table layout of PM, but do not support CSS. Or is Netscape 4 still supported? MSIE 3? Opera 5? In that case, I can only say that I think such a decision is a bad one, and express my sympathy for PM developers. Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }	[reply]