Dealing with "broken" web sites
There has been a discussion going on in Seattle Linux List about sites that don't work with Open Source browsers. I think these guys are barking up the wrong tree.
Telling General Motors that their web site doesn't work with your favorite Open Source browser is not likely to get anything more than a GM person thinking you don't know what you are talking about. There is, however, a better approach. Ok, I think it is a better approach.
Run the W3C complaince tests on the site. (If you have the development plug-in for FireFox) you can check HTML, CSS and more with just a few mouse clicks.) If the site passes, submit a bug report on the browser you are using. On the other hand, if it fails, tell the webmaster than you were having trouble viewing the site so you ran the W3C complaince test and found some errors. (Or 500 errors. Or ...)
Free DevOps eBooks, Videos, and more!
Regardless of where you are in your DevOps process, Linux Journal can help!
We offer here the DEFINITIVE DevOps for Dummies, a mobile Application Development Primer, and advice & help from the expert sources like:
- Linux Journal
- Be a Mechanic...with Android and Linux!
- New Products
- Users, Permissions and Multitenant Sites
- Flexible Access Control with Squid Proxy
- Security in Three Ds: Detect, Decide and Deny
- High-Availability Storage with HA-LVM
- Tighten Up SSH
- Solving ODEs on Linux
- DevOps: Everything You Need to Know
- Non-Linux FOSS: MenuMeters