Full Article Attached BugDay is Moving!

Tuesday May 29th, 2001

Asa Dotzler writes: "BugDay is moving. More than a year and a half has passed since the fist Tuesday BugDay and it seems like a good time to change. Starting this week (tomorrow, 05/30/01) BugDay is moving to Wednesdays." Click the full article link to find out more about BugDay, and how you can get involved.

#36 Re: Re: Re: Jedbro

by AlexBishop <>

Friday June 1st, 2001 11:43 AM

You are replying to this message

"All that matters is hows [sic] it looks not how bad the code is. We need a option for specific websites that look crappy in Mozilla to render as close as it can to IE."

Which version of IE? Version 5? On Windows or Mac? And IE 6 promises to be more standards compliant. Should we update Gecko so it renders badly coded pages like IE6? In that case we may as well disband the W3C and let Microsoft set Web standards. Or should we have an option to make badly coded pages render as they do in Netscape Navigator 1.x, 2.x, 3.x, 4.x? Best add support for Opera-like rendering as well. And NCSA Mosaic. And any other browser you care to think of.

Supporting rendering options for all those browsers is going to be time consuming. Wouldn't it be great if there was one set of standards that we could just obey. Oh yeah, there is. The W3C standards. <>

Early on in the development of Mozilla Seamonkey, the decision was made to obey Web standards as closely as possible. Support for non-standard 'extensions' - be they from Netscape, IE or any other browsers - was dropped. The idea being that it would make it easier for Web developers to code pages and accelerate the expansion of the Web into areas such as PDAs, set-top boxes and Internet fridges (think coding for IE on Windows and Mac is hard? Try Windows, Mac, PDAs, set-top boxes, Internet fridges...)

Even Microsoft acknowledges the importance of standards. Each version of IE is successfully more standards compliant. Eventually, IE's rendering engine(s) may be as standards compliant as Gecko. And then page authors will have to update their pages to standards whether they like it or not. So they may as well do so now. It's quite simple to make pages that conform to standards but still render well in IE and Navigator 1-4.

Supporting IE's 'standards' is impractical, likely to only have short term gains and could slow down the adoption of Web standards. It's just not worth it.

Non-NewZilla Alex