I was trying to view this page: http://www.belkin.com/IWCatProductPage.process?Product_Id=15...I got this error: Error 500 - Internal Server ErrorI get that error only when using Safari. I've tested Safari on Mac, Windows, and on my iPhone, and they all get the error.But the same page works when I use a different browser.I can understand how a rendering error can be browser specific, but how can a server-side error be browser specific?Here's a screenshot of the error: http://dl.dropbox.com/u/74164/Beklin.png
FWIW, I get the same error message when I try to view the page using FF on a Windows machine.
I realized I hadn't tried Firefox, so I tried it on my Mac.Same error using FireFox 12.But it works fine in Chrome 19.
Again, FWIW, I tried it again using FF and this time I got the page OK. But, when I opened the Error Console in FF, a whole bunch of errors were listed. Maybe Chrome is ignoring the errors?
Works for meSafari 4.1.3FF 3.6.28Mac iBook G4The website needs to be validatedResult: 117 Errors, 15 warning(s)http://validator.w3.org/check?uri=http%3A%2F%2Fwww.belkin.co...Denny Schlesinger
Works for meI sent them an email, and they fixed the problem.
It still does not validate117 Errors, 15 warning(s)Send them another email, maybe they'll fix it. ;)Denny Schlesinger
It still does not validateIf it renders properly in all test browsers, does it really matter if the code passes a validation test?Yes, valid HTML code appeals to me, but I don't think any company in the US is going to fix invalid (but working) code just to appeal to my inner pedant.
I wonder which is easier, creating valid HTML or testing all browsers.
I wonder which is easier, creating valid HTML or testing all browsers. Given that the browsers still have differences in their rendering (especially when there are plenty of users still on older browsers that may not render "valid" HTML properly), that's kind of a moot point.I don't care whether it validates to fit the standards or not -- I'm still going to test it in the browsers.dsbrady
An important consideration is the ability of robots to read the website correctly. As far as I know one can't test the robots so one has to rely on valid code. People forget that half the website's audience are not people but robots!Denny Schlesinger
An important consideration is the ability of robots to read the website correctly. As far as I know one can't test the robots…If you want to see if Google's indexing robots read the site correctly, try searching for words on your website, and see if it finds it.so one has to rely on valid code. You're assuming that the robots can properly parse valid code.
You're assuming that the robots can properly parse valid code. Or, more importantly, that they can't parse invalid code.dsbrady
You're assuming that the robots can properly parse valid code.I love it when the competition craps up their websites. It makes life easier for me. Like running against handicapped horses. ;)Denny Schlesinger
Using valid code improves your chances of the site rendering properly across browsers but it is not a guarantee because browsers are buggy too.And the standard that defines what is valid isn't without shortcomings, making the whole thing even more interesting.
Best Of |
Favorites & Replies |
Start a New Board |
My Fool |