Slashdot Mirror

I should have probably posted a link to this in my other post, but anyway:

Browser Javascript Compatability, Browser DOM Compatability, Browser CSS Compatability.

As you can see, the problem is clearly not FF (or Mozilla, anyway). It's most probably bad code written to work on IE, which won't work on the standard-obeying browsers.

I should have probably posted a link to this in my other post, but anyway:

Browser Javascript Compatability, Browser DOM Compatability, Browser CSS Compatability.

As you can see, the problem is clearly not FF (or Mozilla, anyway). It's most probably bad code written to work on IE, which won't work on the standard-obeying browsers.

No, it IS light years ahead of IE.

Unfortunately, IE cannot render properly coded HTML/XHTML/CSS, and therefore webmasters make buggy pages to appear correct in IE.
This means the buggy pages appear buggy in FF, which is just how they should appear, causing many people to think FF cannot render and IE is therefore better.

Once (and if) IE is booted off the top spot, you will see a vast majority of webmasters changing their crappy code for something which actually works right.

IE is paticularly bad for CSS (especailly CSS3) - This confirms that, Although FF isnt on the list, check out the Mozilla column compared to IE.. see what I mean?

The devious thing about this exploit was that the user style sheet the malware stuck on my computer contained CSS property values computed using Microsoft's proprietary expression feature for dynamically computing property values. Specifically, within an expression giving the value of some attribute for the BODY tag, it was looking up certain keywords within the META tag, and if it found them created a pop-up window which took over the entire screen!

Sorry that you page looks not transparent in either MSIE for Mac or Safari or firefox.

you can learn more about opacity from http://www.quirksmode.org/css/opacity.html

if you want to learn more about CSS, you can try http://www.quirksmode.org/css/contents.html

Good luck.

Sorry that you page looks not transparent in either MSIE for Mac or Safari or firefox.

you can learn more about opacity from http://www.quirksmode.org/css/opacity.html

if you want to learn more about CSS, you can try http://www.quirksmode.org/css/contents.html

Good luck.

But if you would like to know more about compatibility, quirksmode.org could be useful.

Becareful, some test may crash your IE6.

I have found that Quirksmode's section on older browsers to be very useful, especially detailing how simple it is to install multiple versions of Internet Explorer. You really do see a jump in CSS and Javascript support as you progress from 3 -> 4 -> 5.01 -> 5.5SP2 -> 6SP1, though I feel this is to be expected.

Now if you'll excuse me, I must be off to try and figure out why the changes I made friday night to work around some invisible transparent layer that was killing all of my links in Mozilla has now created the exact problem in Opera....

This is not insightful, it's name-calling and pejorative ranting.

The OP said:
>The sole reason is that Safari's output is immaculate.

In your haste, you've imputed motives to him that were not in his post.

The reply chastised him for using a browser that, while it may be standards compliant and render beautifully, is used by a small minority web users. The Quirks Mode web site details bugs in the implementation of IE and most other browsers. The fact is that no one piece of software perfectly implements any complex standard. Even if your code is 100% standards compliant it may not display properly in IE due to an IE bug. Thus, to use your numbers, only 5% of people could properly view it. So the sensible course for any serious web author is to check their site, at least once in a while, in the most popular browsers, regardless of their personal feelings about the browsers themselves.

Juse because someone disagrees with you doesn't mean they are dumb. It doesn't mean that you're dumb either. A little civility isn't such a bad thing.

Code after the standards not browsers, try to make the code as semantic as and always use a proper doctype, i usually recommend a sctrict-dtd.

but when choosing a doctype, you choose you should choose one that triggers the standard compliance rendering mode in the diffrent browsers. see here for a list http://www.hut.fi/~hsivonen/doctype.html

Quirksmode.org is a nice place to check out which javascript and css properties that is supported in the diffrent browsers. this css overview has been very helpfull http://www.quirksmode.org/css/contents.html

Code after the standards not browsers, try to make the code as semantic as and always use a proper doctype, i usually recommend a sctrict-dtd.

but when choosing a doctype, you choose you should choose one that triggers the standard compliance rendering mode in the diffrent browsers. see here for a list http://www.hut.fi/~hsivonen/doctype.html

Quirksmode.org is a nice place to check out which javascript and css properties that is supported in the diffrent browsers. this css overview has been very helpfull http://www.quirksmode.org/css/contents.html

I am aware of nonconformities to the latest CSS standards.

Look at this chart. Just scroll down and skim the list. See all that purple in the first and second columns? Those are all things that IE doesn't do properly. Check out the third column from the right, Mozilla. Not much purple there at all.

Or try here. Scroll down and look at all of the non-green in the first column (IE 6). Compare it to Gecko (Mozilla).

Even better, try this one. Be sure to use the blue arrows at the bottom right to go through all of the pages. Compare IE6 to Netscape 7 (Mozilla).

I'm going to have stop here because I just can't stop laughing. Try and code a webpage sometime, you'll see how bad IE is. I think a better question to ask is "What CSS standards does IE comply to?"

However, as a browser, it is one of the browsers that will render even partially received information (or broken HTML) correctly.

Really, I hope you were joking...

Jerk City Troll, you are so abrasive. There really are much better ways to make your point. It's so unpleasant to read anything you post.

Understated, DHTML is difficult. However, in my experience, if you adhere to XHTML and can get your code to work in Mac IE5 and Netscape 4.7 then it will work in %99.9 of the browsers out there (not %100 because I havn't tried them all).
People often slam Netscape 4.7, but truth be told it is an excellent yard stick to measure your code against. The reason why is because it fails on bad code instead of trying to compensate for it. It DOES support DHTML, but the the support is lacking. However, despite the lack of support you can still do many nice things with it. I have.
I'm also surprised that in a discussion of DHTML no one has linked to Quirksmode, which is extremely useful.

Actually you should check this great page which provides performance data for a few DOM operations. http://www.quirksmode.org/dom/innerhtml.html