It will be easy to integrate to Ext.Net for example Ext.IsSupport....
This is not a straightforward as it first might appear. The current list of supported desktop web browsers covers a huge percentage of what users/clients would be accessing Ext.NET with. Probably 95%, maybe higher. The list of supported browsers is so high that it actually rarely comes up as an issue.
There are defects discovered specific to individual browser versions (usually IE7 & 8), but they're still supported.
By testing for .IsSupported we run the risk of excluding something that might be supported, especially new browser releases. We would mostly just test for simple things like IE5.5 or older, older versions of Firefox, Safari and like. The counter to that technique is that those browsers represent a minuscule portion of what's being used, that extra .js required does not offset the benefit.
There is an argument to be made for testing for "Compatibility Mode", so I'll think about that. There's also a case to be made for testing if the user-agent is a mobile browser, although I'm reluctant to include this.
For example do you support IE7, Safari, Opera, Safari mobile, webkit engine
IE6 to IE10 = yes, but not "Compatibility Mode"
Safari = yes
Opera = yes
webkit engine = yes
Firefox = yes
Safari mobile = mostly, but some drag/drop and scrolling functionality is still a problem. Combination of defects in Safari and not supported features of Ext JS. We're hoping to have these fixed shortly after the v2 release, probably v2.1.
We'll make this list more prominent on the
http://www.ext.net/ website.
Hope this help.