Post frame issue Thread

The [*]are outside of the post box.

Happens here too...

Wuggawoo had this, its firefoxes strictness :p

Heres how to fix it, wuggawoo has it fixed afterall :p

li
{margin-left: 2em;}

Not here

/me trys other browsers :o

I thought it was a design feature

Yeah it's Firefox.

this web page is not W3C conform so extecpt things to break with W3C conform browsers ^_^

jacksonj04 wrote: I thought it was a design feature

Yeah it's Firefox.

Same here. It does look different anywhoo.

firefox wants things UBER PERFECT

/me hugs opera

azz0r wrote: Wuggawoo had this, its firefoxes strictness :p

Heres how to fix it, wuggawoo has it fixed afterall :p

li
{margin-left: 2em;}

you and your wuggawoo fixes heh

w00t MSN actually did something right

Opera is teh sux0rs.

it's odd.. i only got it on 40oz's post

Hmm... it seems problems with coding appear to happen frequently on Firefox (or anything outside of IE/Netscape/MSN/AOL), since there were problems with our forums that could only be seen through Firefox. I mean, it's nice to know about them and all, but I guess it just means that FF still has a while to go to work everything out.

40ozFreak wrote: Opera is teh sux0rs.

Firefox requires a website to be 100% top notch valid HTML/XML/CSS

Granted thats a good thing, people might want to get it "PERFECT" for firefox, but not everyone uses firefox, but at the same time alot do use it

Firefox is a W3C compliant browser. This means it only accepts W3C compliant pages, which is what this web needs, that's what W3C is for.

so if pages brake on Fx then they are NOT W3C compliant and not Fx not uber perfect but all others accepting it damn lazy.

standards are there to be followed. if you ignore them by will you just create another mess... and the web is filled with mess.

and opera sux... payware...

Firefox isn't 100% W3C compliant, it has a couple of quirks (I think there's one to do with page borders depending on if the CSS is embedded or imported), but it is the most compliant browser for PCs and in the top of the pack for *nix.

Your problems lie in the fact that IE, Opera, Netscape and co are NOT W3C COMPATIBLE. In theory IE should switch into compatability mode if there's a doctype definition - it doesn't.

Code your page then VALIDATE IT with the free W3C checker (http://www.w3c.org - they have CSS and HTML/XHTML verifiers). If there's no errors, then Firefox displays it *exactly* as it should be.

So all of you use Firefox (link in my signature) and if a page doesn't look right then screenshot it and email the webmaster. Come on, lets get the web standards compliant!

FF rules.. plus ure all gonna need it to use my ModDB-Toolbar so listen to good old jacksonj04

jacksonj04 wrote: Code your page then VALIDATE IT with the free W3C checker (http://www.w3c.org - they have CSS and HTML/XHTML verifiers). If there's no errors, then Firefox displays it *exactly* as it should be.

soooo true. that's why i have those nice w3c logos on my page...

* sooo proud of beeing w3c compliant ^_^ *

Most of the internet is coded to suit IE viewing requirements, and thus is not W3C compliant as it should be. This is what causes the errors in Firefox.

don't tell me... i nearly got the flue testing my page once on IE... it was HORRIBLE!!! i had to change all the nice little sneaky html code pieces just to give poor people with CrapExplorer the chance to view it somehow usable.

* burns IE until it's no more than a black brick...

Internet Explorer is not a good browser, it's just the one everybody has shoved down their throats, so they give up and use it.

IE doesn't make the code. The coders do. I don't see your point...

If it's coded almost perfectly, it should be fine in either browser.

It should, but IE doesn't meet W3C validation standards for page formatting

little notice. it is not the html writers that have troubles with IE, it is IE who allows incomplete and incorrectly formated html tags. that's the problem.

that some browsers do things display a bit different is not a big problem usually. but if you have browsers eating any wrong tag html writers write their pages in that faulty code as they don't know that they do something wrong indeed.

that's the problem. i hope web designers wake up a bit and start producing w3c standard pages... and using the w3c tag on their page to encourage others to do it the same.

I validate as much as possible, then hack in as much valid code as I can to get IE to render them properly.