[Mono-dev] Problem with Request.Browser.MSDomVersion and Firefox

Marek Habersack grendello at gmail.com
Tue Apr 24 15:48:33 EDT 2007

On Tue, 24 Apr 2007 21:51:38 +0300, "Adar Wesley" <adar.wesley at gmail.com>

> Hi Hubert,
Hey Adar
> We recently implemented all the missing capabilities in the
> HttpBrowserCapablities class.
> During the implementation we implemented this throw to be compatible with
> MS.Net which
> throws if the capability isn't defined at all.  The code is based on the
> assumption that the
> browscaps.ini file should contain the correct values for all the common
> browsers.
> However, this is not the case!  Since browscaps.ini has it's own maintainer
> we did not update
> that file.
That's not entirely true, we do update it to add the ecmaversion entry to some

> In order to fix this problem add the missing definitions to the
> browscaps.ini file.
I have committed today a fix that provides defaults for the browser caps if
they are missing from the definition or browsercaps.ini is broken/missing. Even
if Microsoft .NET throws an exception in that case, I don't like the behavior
as it is completely unjustified imho. If you want Mono to still throw the
exception in case caps are missing, we can add an environment variable that
will turn the MS.NET behavior on.

best regards,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070424/28ea330c/attachment.bin 

More information about the Mono-devel-list mailing list