Google Zeitgeist Browser Stats Now Recognise 'Netscape 5.x'
Thursday February 20th, 2003
FriedEgg writes: "'Netscape 5.x' (Mozilla based browsers) are now listed separately in the Google Zeitgeist, and no longer grouped into 'Other'."
Targeted at members of the press and the curious, Google Zeitgeist offers regular statistics on the trends, patterns and surprises found by analysing Google search data. Following on from a discussion in our forums, MozillaZine reader jgraham has been in touch with Google, who say that 'Netscape 5.x' represents "all versions of Netscape 5.0 and newer and anything that uses Gecko."
#24 Re: Designing for IE
Saturday February 22nd, 2003 11:11 AM
You are replying to this message
"What about the fact that IE and Mozilla can't use the same plug-ins? Mozilla uses np*.dll and XUL jars, while IE uses ActiveX controls."
A site can be designed to use Flash, Real, Java, etc. and work fine in both IE and Gecko-based browsers. Besides, none of that falls under the "develop for the standards" suggestion that your post is in response to.
"What about IE's inability to view MNG animations out of the box?"
Nobody's perfect. Neither Gecko nor IE support every standard fully. Developing for the large and growing subset of the standards that both IE and Gecko supports seems like a prudent and time saving approach.
"What about the errors in IE's interpretation of CSS, especially relating to whether or not the border and padding are included in the box dimensions? W3C says they MUST NOT but IE includes them anyway."
Like I said, there's a large and growing subset of standards that modern browsers do support. Developing with that subset seems to be a good approach.
"What about the fact that instead of interpreting XHTML sent as application/xhtml+xml as XHTML, IE 5 and 6 both display a source tree view?"
Is that true even if you reference an appropriate style sheet with the content? I'm no web developer but it seems like there are pretty trivial ways to work around most browser quirks without forking the whole web page/site. I see your point, that developing for the standards might leave IE users with a less than ideal experience but there's certainly a useful subset of the agreed apon standards that web developers can use and successfully target Gecko, IE, Opera and others (excluding the generation 4 and older browsers).