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 ...)
|diff -u: What's New in Kernel Development||Sep 04, 2015|
|Android Candy: Copay—the Next-Generation Bitcoin Wallet||Sep 03, 2015|
|The True Internet of Things||Sep 02, 2015|
|September 2015 Issue of Linux Journal: HOW-TOs||Sep 01, 2015|
|September 2015 Video Preview||Sep 01, 2015|
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
- diff -u: What's New in Kernel Development
- Using tshark to Watch and Inspect Network Traffic
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- The True Internet of Things
- Android Candy: Copay—the Next-Generation Bitcoin Wallet
- September 2015 Issue of Linux Journal: HOW-TOs
- Firefox Security Exploit Targets Linux Users and Web Developers
- Concerning Containers' Connections: on Docker Networking
- Where's That Pesky Hidden Word?
- A Project to Guarantee Better Security for Open-Source Projects