[Mono-bugs] [Bug 74777][Nor] Changed - HttpBrowserCapabilities does not detect IE properties correctly

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by flashdict@gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74777

--- shadow/74777	2005-04-30 17:22:26.000000000 -0400
+++ shadow/74777.tmp.3767	2005-05-03 17:33:43.000000000 -0400
@@ -99,6 +99,34 @@
            
             
         </form>
     </body>
         
 </html>
+
+------- Additional Comments From flashdict@gmail.com  2005-05-03 17:33 -------
+Mono determines which browser is connected via the browscaps.ini file,
+which is installed in /usr/local/etc/mono on my machine.  This file is
+produced by one Gary Keith (http://www.garykeith.com/index.asp), and
+even in the most recent version, does not include specific definitions
+for BrowserCapabilities.Win32, which is why your test is failing.
+
+You are correct though, in that a recent change by Gonzalo Javier to
+the System.Web.HttpBrowserCapabilities.cs did indeed formalize the
+method to obtain the Win32 boolean.  Previously the code simply
+assumed that if the browser was not Win16, then it was Win32, which
+may be the best way to set the variable, given the lack of Win32
+definitions in Keith's browscaps.ini file.
+
+In any case, as regarding mojoportal and the FCKEditor, I think it
+should only be necessary to test for the existence of
+oBrowser.JavaScript (along with the Major version and IE test) to
+decide whether to load the FCKEditor.  Although you could use
+oBrowser.ActiveXControls if you really must know if it's a "Authentic
+IE" which is connecting.
+
+The only possible "fix" I can see here is if Keith updates his ini
+file, or alternatively if Mono begins to update it within the project,
+or if Gonzalo's change to HttpBrowserCapabilities.cs is reverted.
+
+Bill
+