how-to block ads
|
JAAulde
yum yum yum yum yum
Premium,MVM
join:2001-05-09
Hagerstown, MD
2 edits | reply to jDyno
Re: Dvorak embarrasses himself on CSS instead of Macs this time
Dvorak is making himself look like an idiot. Now, don't get me wrong--developing cross browser compatible sites can be frustrating. I'm not dogging Dvorak for ranting about browser differences. But to take his platform and mis-represent this technology has knocked him down a few more notches as far as I am concerned.
First, you don't get mad at the technology. You might get mad at the vendors who are not implementing it properly, but not the technology.
Second, for the most part, there really aren't that many difference between the browsers. And it isn't only in CSS where you find differences. It's in (x)HTML, CSS, JS and so on. But again, this is due to the vendors interpreting things differently, or simply going against the grain hoping their version will get more popular and cause their software to gain ground (cough, MS, cough).
Third, differences that do exist are correctable if you understand the technology. For example, to quote KoolMoe  :
said by KoolMoe :
How come IE and Mozilla work with padding/margins differently? Doesn't the standard specify how that should be dealt with? If not, why not!
IE and the other guys have different 'box models' from each other when IE is in 'quirks' mode. Take IE out of quirks mode and things get much better. How do you get IE out of quirks mode? Ensure your DOCTYPE is valid and is the absolute first bit of text (no white space ahead of it either) in your served page. Answering the question as to why there are differences when IE does things its own way, see the above paragraph about vendors who go against the grain.
Next, quoting Dvorak:
said by Dvorak :
The first problem is the idea of "cascading." It means what it says: falling—as in falling apart. You set a parameter for a style element, and that setting falls to the next element unless you provide it with a different element definition. This sounds like a great idea until you try to deconstruct the sheet. You need a road map. One element cascades from here, another from there. One wrong change and all hell breaks loose.
Let me paraphrase him: "I don't know CSS so when it breaks I don't know what to do. This is the fault of CSS." 
Finaly, finishing that quote, this comment is absurd:
said by Dvorak :
If your Internet connection happens to lose a bit of CSS data, you get a mess on your screen.
Ummm, sure. And if your connection drops some HTML, same thing. Oh yeah, and some JS--yeah, that breaks if you drop bits to. Welcome to the Internet. If your crappy connection drops data, the stuff you did get acts weird. Reload for Heaven's sake!
Edit: for clarification
--
"There's a war going on insdie me--the good fightin' against the evil. But I thank God for redemption."
--Johnny Cash
| |
insomniac84
join:2002-01-03
Schererville, IN
| said by JAAulde :this comment is absurd: said by Dvorak :
If your Internet connection happens to lose a bit of CSS data, you get a mess on your screen.
Ummm, sure. And if your connection drops some HTML, same thing. Oh yeah, and some JS--yeah, that breaks if you drop bits to. Welcome to the Internet. If your crappy connection drops data, the stuff you did get acts weird. Reload for Heaven's sake! Edit: for clarification Yea, I was kinda weirded out reading that. It's just like saying the RAR format is flawed because a glitch with my internet connection or browser corrupted the file and therefore I can't extract it. | |
RARPSL
join:1999-12-08
Suffern, NY
| reply to JAAulde
said by JAAulde :Third, differences that do exist are correctable if you understand the technology. For example, to quote KoolMoe : said by KoolMoe :
How come IE and Mozilla work with padding/margins differently? Doesn't the standard specify how that should be dealt with? If not, why not!
IE and the other guys have different 'box models' from each other when IE is in 'quirks' mode. Take IE out of quirks mode and things get much better. How do you get IE out of quirks mode? Ensure your DOCTYPE is valid and is the absolute first bit of text (no white space ahead of it either) in your served page. Answering the question as to why there are differences when IE does things its own way, see the above paragraph about vendors who go against the grain. Query - If I am creating XHTML Pages and start them with:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
in lieu of just:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
does this mean I am going to get Quirks mode or is IE smart enough to ignore the <?xml and treat the <!DOCTYPE as the first thing it "sees" and thus go into Standards Mode? | |
JAAulde
yum yum yum yum yum
Premium,MVM
join:2001-05-09
Hagerstown, MD | You will get quirks mode. Thus my topic here: »Stickler for standards? Declare your XML!
--Jim | |
|
