Welcome to AOL.COM AOL has joined the ranks of mega sites moving to valid CSS page designs. Can’t get much more mainstream than that.
Category: browsers
Mac screen shots for the other 97% of the world
iCapture – your site through the eyes of Apple’s Safari browser. Oh, and IE now too. Now Windows-only folks can see how your site looks to a Mac user with this great service.
Once was never enough
Until now, one version of Internet Explorer at a time was all a poor Windows machine would allow. So testing Web pages in various versions of IE was a problem for many designers. Well, someone discovered a way to have more than one version of IE running on a single Windows machine. Chicago Web Design – Insert Title Web Designs made the leap and tells all.
Many versions of many browsers are available from Evolt.
Tip: If it’s yellow it must be Google
I recently learned from my highly valued Wise Women friends that the source of my yellow form fields was the Google Toolbar. I had been searching my HTML and my CSS for some explanation as to why my form had yellow backgrounds in some of the text fields. Turns out that the Google toolbar (which I like and am not knocking) has an autocomplete option in the Options area. If autocomplete is turned on, the Google toolbar indicates form fields which it will autocomplete by making them yellow. This also explains the mystery of why the form fields looked yellow in Windows but not in Mac, as the Google toolbar doesn’t work in Mac browsers.
The Master Grid is Dead. Long Live the CSS Support Charts!
CSS Support Charts The much loved Master Grid of CSS and various browser support for it has gone away. But Netscape devedge to the rescue with the same info restored to its full glory. Browser support for CSS specification and some CSS 2 specs.
See your site in any browser
Browser screen captures in any browser, any version, any operating system. Not free, but a terrific service anyway, check it out.
Tip: Turning off cache in Mac OS X Safari browser
A former student sent along this tip for ridding Safari of persistent cache problems when testing new Web pages.
1. Delete the Safari cache folder. This should be in ~/Library/Caches/Safari/.
2. Create an empty text document and save it as ‘Safari’ (no extension) and place in ~/Library/Caches/. The name of the file must match the name of the old folder, thus preventing Safari from making a new one.