We found consistent and reproducible issues in CSS3 Animations and CSS3 Transitions among other things. We had issues where the browser either hung or crashed. Regular scrolling was slow or below full framerate. We had issues where media playback failed or performed incorrectly. At times it felt like we were using a preproduction device, but we bought our test device from a Verizon Wireless store.
Harsh words. Sencha was quick to note the finer things about the Motorola Xoom browser before dropping their complete analysis bomb on everyone though. The Motorola Xoom led the pack during the SunSpider test due to its use of a more recent WebKit build. After that, well -- the Xoom in their minds bit the dust despite obtaining perfect score on the Acid3 tests as it still failed to render the letters and numbers, as it should have.
So should this turn a user off from buying a Motorola Xoom -- or leave a bad impression of the device overall? Not really. The tests completed by Sencha were done so based on their business background being the development of HTML5 applications. Unless you're intending upon developing HTML5 applications you'll likely not be as concerned as they were with the browser's abilities.
That said, it does add some credibility to those who have stated the Motorola Xoom was rushed out the door. But, hopefully Google and Motorola will continue to work out the kinks, I mean we already have to ship the device back to them anyway. Least they could do is load a new browser. Makes me wonder how Firefox would run on it. Full report is available at the source link should you want the nitty gritty details. [Sencha via Daring Fireball]
- Filed under: