3 ms·
It's quite possible that there's a valid technical reason for this. Codec usage? Something bleeding edge to do with HTML5 Audio? A slightly crappy but plausibl
by andybak 15y ago
It's quite possible that there's a valid technical reason for this. Codec usage? Something bleeding edge to do with HTML5 Audio?
A slightly crappy but plausible reason is that they didn't want the extra hassle of cross-browser testing and pool of browsers capable of running this was pretty small.
- jarin 15y agoOr the simplest explanation is that they wanted people to install Chrome to be able to see it.
- zobzu 15y agoThe explanation is of course that they want people to run Chrome no matter the cost. They can force people to upgrade to chrome that way. It's a well known way of doing stuff. Microsoft has done that for ages in the past and got bashed for it until they started to fall. When Google does it, it's ok tho. Figures. ps: this is actually doing evil
- pornel 15y agoWhatever the reason, the implementation is broken — it sniffs User-Agent and blocks everything else than Chrome. If I change Chrome's User-Agent string to Safari, then this site blocks even Chrome: http://yfrog.com/z/kh1rylsqj http://yfrog.com/z/kh1rylsqj