A Comparison: Microsoft Surface and iPad 4
The Microsoft Surface and the iPad 4 now join the iPad 2 and the RIM Playbook 2 as impressive HTML5 tablet platforms
By: Michael Mullany
Dec. 4, 2012 07:30 AM
The Microsoft Surface
We'll also note that if you plan to evaluate the Surface yourself, it's *essential* to upgrade the pre-installed Office Preview to the release version. Before upgrading, entering text was absurdly and unpredictably laggy not just in Office, but also in browser-based input fields.
If you're looking for Surface traffic, its user agent is: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; ARM; Trident/6.0; Touch)
IE10 has a new collection of CSS properties and events to control touch event handling. Many HTML5 apps will want to use the ms-touch-action: none, to suppress OS pre-emption of touch events within their app. WebKit style touchstart, touchend etc. are not available. Instead we have Microsoft's new pointerEvents, which unifies mouse and touch events under one roof. The Surface has a rock-solid implementation of position: fixed, and even makes a college try of supporting background-attachment: fixed - which Mobile Safari still ignores.
HTML5 feature coverage
There are some notable omissions and deficiencies compared to the iPad 4. There is no support for the input tag for camera or video capture (introduced in iOS 6), the flexbox implementation is the older, superseded version. There is no border-image support (admittedly the border-image support in mobile Safari is not completely correct either.)
Neither platform supports WebGL, but Microsoft has previously said that it won't support it. Nor were the more esoteric HTML5 inputs like color supported. Notifications and server sent events were likewise absent from both platforms.
SVG Support & Performance
The SVG implementation in IE10 on the Surface is rich with a full complement of SVG features. It's fantastic, for example, to see broad support for SVG filter effects like color channel manipulation. We did notice a few minor blemishes. The performance of the lighting effects we tried was very poor (10s+) and the feSpotlight primitive was not supported. Lighting effects were noticeably darker than the reference SVG test images. And although Modernizr reported SMIL support, we were unable to get any declarative SVG animation to run successfully. SVG Filter effects are also imperfect on Mobile Safari, and anyone looking to use them should expect vigorous testing and cross-browser normalization.
Microsoft's own fishbowl demo was also a good stress test of real world canvas use. This demo composites multiple separate canvas contexts together on top of a background video, with sound effects in a separate audio element. There are also CSS transforms and CSS opacities present. With all effects disabled except basic sprite animation, the Surface managed about 110 concurrent sprite animations at 60fps, while the iPad 4 managed about 135. Strikingly, when we enabled more effects (masks, background, shadows and more.), the iPad 4 held up well while the Surface struggled. With all effects enabled except the background water video, shadow effect and audio, the iPad 4 could support about 100 concurrent sprite animations at 60fps, whereas the Surface was able to support only 10. Canvas compositing appears to be a particularly challenging graphics operation for the Surface vs the iPad.
An Embarrassment of Tablet Riches
Reader Feedback: Page 1 of 1
Latest AJAXWorld RIA Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week