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 ...)
|Nativ Disc||Sep 23, 2016|
|Android Browser Security--What You Haven't Been Told||Sep 22, 2016|
|The Many Paths to a Solution||Sep 21, 2016|
|Synopsys' Coverity||Sep 20, 2016|
|Naztech's Roadstar 5 Car Charger||Sep 16, 2016|
|RPi-Powered pi-topCEED Makes the Case as a Low-Cost Modular Learning Desktop||Sep 15, 2016|
- Android Browser Security--What You Haven't Been Told
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Nativ Disc
- The Many Paths to a Solution
- Naztech's Roadstar 5 Car Charger
- Synopsys' Coverity
- Securing the Programmer
- RPi-Powered pi-topCEED Makes the Case as a Low-Cost Modular Learning Desktop
- Glass Padding
- Identity: Our Last Stand