Fixed - Cant see all text on some threads
by Billy L · in Site Feedback · 12/16/2005 (11:47 pm) · 26 replies
On this thread i cant see the hole text , it cuts in the right margin .
Check this
I tried to refresh and reload it but nothing helps.
Check this
I tried to refresh and reload it but nothing helps.
#22
Also, testing: averyverylongstringofcharacterswithnospacesinthemwhatsoeverthatwouldallowittowordwrapbeforeithitstheendofthepagewhereitwillpushbeyondtheexpectedwidthbreakingthepageandmakingmuchofthetextunreadablewhichisnotgoodatall
Edit: Ok. That scrolls nicely now.
12/21/2005 (2:52 pm)
Re: Joseph's link: That thread works in my Konqueror 3.4.3 and Mozilla 1.7.12. Although it doesn't really look that great in Mozilla. The font sizes are inconsistent, and there is an excess of scroll bars. Still, it is readable. Also, testing: averyverylongstringofcharacterswithnospacesinthemwhatsoeverthatwouldallowittowordwrapbeforeithitstheendofthepagewhereitwillpushbeyondtheexpectedwidthbreakingthepageandmakingmuchofthetextunreadablewhichisnotgoodatall
Edit: Ok. That scrolls nicely now.
#23
12/21/2005 (3:51 pm)
Surprized it works with Netscape because nothing ever works with Netscape. 
#25
Well, Netscape 7 is just a re-branded Mozilla, and Mozilla's Gecko engine has made very good progress in recent years. I've found it easier to make sites look good in Mozilla than in IE lately. Firefox also is just another shell for the same Gecko engine, so if it works in Firefox there's no reason it shouldn't work in Netscape 7 as well.
If you write code to the W3 specs, it's pretty much guaranteed to work in Gecko and KHTML engines, which covers Mozilla, Netscape, and Firefox (Gecko), as well as Konqueror and Safari (KHTML). Opera as I understand it is also good at following the specs. Then you just have to make sure IE can handle it.
[rant] Now if MS would just get their head out of their *** and write a browser that respects the W3 specs, we'd be all set. I could write code to spec and not worry about which browsers can handle what. The problem is, when coming from an IE background, it looks as though everything else doesn't work. When in fact it's only IE that doesn't work "properly". [/rant]
That of course was not the case in the years gone by, but the situation has changed greatly (albeit rather quietly) in recent years.
12/21/2005 (4:37 pm)
@Rick,Well, Netscape 7 is just a re-branded Mozilla, and Mozilla's Gecko engine has made very good progress in recent years. I've found it easier to make sites look good in Mozilla than in IE lately. Firefox also is just another shell for the same Gecko engine, so if it works in Firefox there's no reason it shouldn't work in Netscape 7 as well.
If you write code to the W3 specs, it's pretty much guaranteed to work in Gecko and KHTML engines, which covers Mozilla, Netscape, and Firefox (Gecko), as well as Konqueror and Safari (KHTML). Opera as I understand it is also good at following the specs. Then you just have to make sure IE can handle it.
[rant] Now if MS would just get their head out of their *** and write a browser that respects the W3 specs, we'd be all set. I could write code to spec and not worry about which browsers can handle what. The problem is, when coming from an IE background, it looks as though everything else doesn't work. When in fact it's only IE that doesn't work "properly". [/rant]
That of course was not the case in the years gone by, but the situation has changed greatly (albeit rather quietly) in recent years.
#26
12/21/2005 (4:50 pm)
@scott W3 Ahmen! 
Torque 3D Owner Stephen Zepp
FYI, I had the same exact problem you did, upgraded, and the problem went away.