Top 10 Browser Types Compiled from Our Aggregated Data
Over the Past 3 Months (Last Updated June 1, 2008)
| Browser |
Hits |
Percent |
|
|
| Microsoft
Internet Explorer 7.x |
|
43.61% |
|
| Microsoft
Internet Explorer 6.x |
|
33.20% |
|
| Firefox x.x |
|
16.10% |
|
| Safari x.x |
|
5.90% |
|
| Mozilla |
|
0.35% |
|
| Opera
x.x |
|
0.30% |
|
| Netscape x.x |
|
0.17% |
|
| Microsoft
Internet Explorer 5.x |
|
0.13% |
|
| |
|
|
|
| |
|
|
|
A word about
Web browser standards
A number of elements and practices considered "standard" among
web developers for adding HTML and/or cross-browser support
to their web pages were recently excluded from the W3C HTML
4.0 and Document Object Model specifications. Tags like
<LAYER>
<MARQUEE>
<BLINK>
<BGSOUND>
These are just some of the tags that no longer
work in many of the new web browsers. In addition certain
objects like document.layers[] and document.styleSheets[],
for example, are actually not a part of any web standard.
Using standards in your web development makes your pages
genuinely cross-browser and cross-platform, makes them a
part of a coherent and robust document object model, makes
them readable and extensible by others, and also furthers
the cause of the standardization process itself.
Developing
Cross Browser/Cross Platform Pages and Serving them by
Sniffing
An important practice for doing cross-platform
development is to able to determine at runtime the capabilities
of the browser that are viewing your page. You need to avoid
errors, and may want to ensure your script reaches as wide
an audience as possible.
This process, often referred to as "browser
sniffing," is usually handled by JavaScript functions that
test the version and type of the browser and, if necessary,
use different functions or point the user to different pages
or web content as shown by the schematic below:

Alternatively the "browser sniffing" code
can function to deliver browser specific content within the
same page as shown by the example below:
You have viewed this page with :
|