Tom Holmes wrote:
We override all the .NET properties we have reliable data for. For the initial release we reduced how much we overriding we were using. Now we feel more confident in the data we will be adding support for the W3CDomVersion and SupportsCallback in the next release.
I see but that seems to be a step back and we must wait for your next release. Your fundation's unique benefit is in the seamless integration with .Net and proper populating of .Net Request.Browser properties. Some of Request.Browser properties are critical in the current .net web apps, especially those which are used by ScriptManager to determine whether or not the device supports partial callbacks. The logic is as follows:
// Simulate Script.Manager.SupportPartialRendering logic
bool supportAjax = (
(Request.Browser.W3CDomVersion >= new Version(1, 0)) &&
(Request.Browser.EcmaScriptVersion >= new Version(1, 0))) &&
Request.Browser.SupportsCallback;
I pointed that out a few months ago you you added appropriate mapping in ver.1.x. Hope to have it in v.2 soon.
Also, I remember in ver.1.x you had a specification describing mapping between Request.Browser and mobile database properties. Can you post it if possible?