However, these stupid programs don't read it properly!!!! don't know why the hell they're being stupid! Netscape gives me black arial text with default size. IE gives me white arial text a bit larger than default??? ***???????????????
Anyone can tell me why these two dumb programs don't work anymore?
::You won't know your limit until you go beyond it...::
Try putting "-1" or "+1" depending on if you are trying to make it larger or smaller than default. I got a nice book that lays it all out and alot of the time things still don't work, its stupid.
Sounds very strange. It probably won't fix the problem, but in the future, always combine your tags, like this:
<font face=Arial size=1 color=#FFFFFF>test</font>
Quotation marks are not required unless you have spaces or multiple values.
It's best practice to always quote your attributes, and yeah, the reason why Netscape was rendering it as black text was because you neglected to put the pound-sign before the hexidecimal color value of white (#ffffff).
You'll find that text in general will render slightly differently in different browsers at times, particularly in older versions of Netscape (4.x). Using CSS styles, instead of font tags often lends you a bit more control over the look & feel of the text, and from my experience, usually helps it look consistant across all browsers. On top of that, the <font> tag itself is officially deprecated, so in-theory you shouldn't even be using it if you wanted to be compliant with the latest HTML standards. CSS is the preferred approach.
Personally, I don't care too much about HTML standards myself, I still sometimes prefer the tride & true table-layouts with invisivible gif spacers - but that's a conversation for another time.
Originally posted by Grizzly Personally, I don't care too much about HTML standards myself, I still sometimes prefer the tride & true table-layouts with invisivible gif spacers - but that's a conversation for another time. [/B]
He he he... hey, no one said this was "deprecated." Lol. Hurra for margin and padding
Yeah I know, but true HTML standard zealots tend to follow strict XHTML specs these days - you know, the whole "seperation of content from style" schpiel. It's a point of view I wholly agree with, but when you're developing a site for a client who wants it to look and act the same in all browsers, going all the way back to NS 3.0 on a MAC, you don't have much choice but to use the old tride & true methods
Reply With Quote
Lol. Hurra for margin and padding 
Bookmarks