Page 2 of 2

Posted: Mon Jul 25, 2005 12:53 pm
by dreamline
LOL.. I still think that all browsers should be confirmed to only 1 standard.. It just sucks that every browser has it's own interpretation for certain items...

Like we have an ISO standard for burning w3 for HTML and CSS standards there should also be something for browsers called ABC (All Browsers Compatibility my idea) for browsers... Don't you just hate when you put in a lot of effort to get something to work and you figure out that some sleezy browser doesn't show a page properly....

I know i do, so that's why i stick to the most used... Untill there's a better standard... LOL

Posted: Mon Jul 25, 2005 3:32 pm
by Roja
Ambush Commander wrote:Maxthon actually looks pretty good from the website. If you want a trimmed down version of Maxthon that has the ability to get all of its features, go for Firefox.

When Firefox 1.5 comes out, we'll start yelling at you to switch. Well, at least you're not using IE.
Sorry, Maxthon *IS* IE, plus additional cruft. Same horribly bad handling of standards, same unacceptable memory leaks, same rendering quirks.

They just smoothed out the user interface issues that IE has.

But I think Dale pretty much answered it.. he's doesn't consider the advantages - he just uses IE regardless of the issues.. even if they cause him (and other developers) specific, documented problems (that deviate from established standards) when developing.

I prefer dealing with reasonable, open minds. :)

Posted: Mon Jul 25, 2005 3:37 pm
by Roja
dreamline wrote:LOL.. I still think that all browsers should be confirmed to only 1 standard.. It just sucks that every browser has it's own interpretation for certain items...
There is one standard. The W3c is the standards body for HTML and CSS. The standards have been out for several years, and every browser tries hard to meet those standards. Not one browser maker has endorsed, or even encouraged an alternative standards body.

That said, there is now effort to 'speed along' new standards in a group called WHAT-WG, which is helping to develop and encourage new ideas into the W3c, like "canvas".
dreamline wrote:Don't you just hate when you put in a lot of effort to get something to work and you figure out that some sleezy browser doesn't show a page properly....
Exactly. Thats why we shouldnt code to anything but standards. If it can't be done in the standards because a particular browser wont support it, either be clear that that browser fails to support standards properly, OR, don't use that technique at all.

Coding to standards ensures that the browser manufacturers will support the standards more.

Posted: Tue Jul 26, 2005 6:59 am
by Dale
Nevermind :D

Posted: Tue Jul 26, 2005 7:09 am
by Chris Corbyn
Roja wrote:Coding to standards ensures that the browser manufacturers will support the standards more.
Exactly! validator.w3.org all the way ;)