View Single Post
Old 01-31-2010, 12:59 PM   #7671
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by zelda_pinwheel View Post
hm, i admit i've not yet tested v.10 too much, but i wouldn't say it was *completely* standards compliant ; there were some (minor but visible) differences in how opera rendered a few of my sites compared with any other browser.
There will be. It's unavoidable.

Quote:
ha !! i wish all the browser developpers would actually get it together and become COMPLETELY standards compliant (or at least agree to be non-compliant on the same things and in the same way, fachrissake), so that i wouldn't have to hack my nice clean code so my site will work the same on all 3 of the sodding things !
Only three?

You have IE, based on the Trident rendering engine, Firefox and SeaMonkey based on Mozilla's Gecko engine, Safari based on Webkit, and Opera based on Presto. And there's Chrome coming up on the outside, but I believe that also uses Webkit.

The developers do talk to each other (save possibly Microsoft), but you'll never see total standards compliance. Problem one is that any standard will have gray areas where two different vendors will come up with two different ways of implementing the standard that will have different results, but each way will be arguably correct as the standard is defined. Problem two is that standards are a moving target. Discussions are ongoing about HTML 5, CSS 3, and future revisions to ECMAScript (JavaScript). Once they get ratified, there will be a whole new area where things will be different between browsers in odd ways.

The best you can hope for is that most things will work the same in any browser, and the number of special cases you need to handle will diminish and be in more obscure areas.

Quote:
lord preserve us from IE's idea of "standard compliant".
Microsoft is like pretty much everybody else: "We firmly support standards! Do it our way..."

Quote:
see, that's the kind of thing that drives me completely MAD.
Yes, but at least I can make a case it's not a browser issue. If it was FF, I'd expect it to crash, or freeze and need to be terminated from Process Explorer. When I have to hit the reset switch and reboot the machine, it points at an underlying system problem.
______
Dennis
DMcCunney is offline   Reply With Quote