Webware 100 (Browsing) – The Finalists
If you would like to support your favorite web browser by voting at cNET Webware 100, feel free to do that now.
Poll includes the following browsers: Camino, Firefox, Flock, Google Chrome, Internet Explorer 8, Lunascape, Maxthon, Opera, Safari, Skyfire and WebKit.
About (Author Profile)
Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded FavBrowser.com. Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.
Opera users should be careful for what they’re voting for, because the page doesn’t render properly in Opera. You could end up voting for Firefox by mistake:
http://img19.imageshack.us/img19/1441/fubarpoll.png
Just click the label… Opera does have got support for the “for” property, doesn’t it?
Also, I’d garner that the radio button you are talking about would send in a vote for Flock and not Firefox.
Can’t really see anything in the code that would cause any problems with rendering, anyone else?
Regarding Kyle’s post, the picture he provided of the page looks exactly the same in IE8. But if you turn on compatibility mode, it will be fixed.
Hmm, problem appears here when increasing the width of the containing box:
http://bayimg.com/dAoaIaaBl
but works fine otherwise
http://bayimg.com/DaoAhAabL
Perhaps this is caused by differences in calculating pixel rounding? Btw, here the markers on the far right are associated with the labels on the far left when the error appears O_o
Since when webkit is a browser ?
It’s technically rendering engine. However, you can download it from webkit site and surf the web anyway.
Whoops. I probably accidentally voted for PageFlakes. Which is something I’ve never heard of before.
With regards to the rendering issue… clicking on the radio button immediately to the left of Opera is actually a vote for Opera (I tested it).
75 Errors, 12 warning(s)
This page did not pass the w3c markup validation… thats why…