Compatibility Tips
Browsers:
Your Audience will determine which browsers you need to support:
- Netscape Navigator/Communicator (2.x, 3.x, 4.x)
- Microsoft Internet Explorer (3.x,4.x)
- AOL (3.x, 4.x)
- WebTV (1.x, 2.x)
Not all versions are created equal--especially for JavaScript, etc. You may need to create code for multiple versions. example
Plug-Ins are not an option for consumers--unless they come pre-installed in the browser.
The only cross-browser standard for media is QuickTime! (for all browsers, but Flash for newer ones).
Design Considerations:
Background offsets are a bitch! You can handle this by:
- Building separate pages for different browsers: example
- Using LEFTMARGIN, TOPMARGIN, MARGINHEIGHT, and MARGINWIDTH tags to try to control the placement of graphics on the page: example
- Building a page as one frame (in which case there is no margin in the frame) or two frames with one hidden. This can cause navigation probelms, however.
You can't count on text placement or sizes in layouts since typeface and size will be different in different browsers. operating systems, and users' settings (and combinations thereof).
Don't use HEIGHT tags for tables with ASCII text--only graphics--since they will change based on the current settings for size in a user's preferences.
Be sure to check your work on all targeted operating systems since most Windows and UNIX machines have no gamma correction and, thus, render graphics much darker.
Where possible, design your pages to flow gracefully into different page sizes. If you use percentages in table widths, frames, and graphics, for example, they can fill the page more fluidly and work for both smaller and larger window sizes. Glenn Davis calls this ice, jello, and liquid design.
Media:
Audio and Video clips (as well as other documents) need to be available in multiple formats:
The only cross-browser standard for media is QuickTime! (for all browsers, but Flash for newer ones).
Never require users to decide which file version is best for them. Wherever possible, sniff their browsers and plug-ins and sen them the best file automatically. If you cannot do this (such as in the case of Shockwave), creating an example and refer to it on the page:"if you can see the ladybug flying around, click here. If not, you need to install Shockwave (click here)."
Operating Systems:
Your Audience will determine which operating systems you need to support:
- Windows
- Macintosh
- UNIX (various flavors)
- WebTV
You need to implement advanced features with grace:
- Be sure that your pages work well in all the browsers your audience uses--even if the advanced features don't.
- Alternate sites, pages, or code for different browsers are possible but a lot of work to maintain. At least, make sure they are served automatically by sniffing browers, versions, and plug-ins.
- Be sure your pages work without images (text-only)--especially if you want international surfers.
Engineering:
You must find a balance between loading the page with code to detech plug-ins and transfer different versions of files (less upkeep) or requiring the server to do this (faster download but will increase the server's load).
Reources:
Project Cool (for JavaScript and server stripting ideas)
Lynda Wienman's site (for design and palette tips)
