On 8/7/2014 15:09, Warren Young wrote:

you can use a <meta> tag to do the same thing

Confirmed. If you go to Admin > Skins > Header, and add this line somewhere in <head>, IE8+ will work in standards mode when you point it at an "intranet" instance of Fossil:

    <meta http-equiv="x-ua-compatible" content="IE=edge" >

I don't think this is the right solution for Fossil out of the box, though, for a bunch of reasons:

1. You'd have to add it redundantly to all the <head> tags in src/style.c, not just to zDefaultHeader.

2. Fixing it here won't help any Fossil installation where they have already customized the page header.

3. It appears that Fossil's SCGI and HTTP server features are built on top of its CGI feature, so one fix applies to all three use cases.

Therefore, I offer this trivial patch, which I hope does not require a signed contributor agreement:

Index: src/cgi.c
==================================================================
--- src/cgi.c
+++ src/cgi.c
@@ -306,10 +306,11 @@

   if( g.fullHttpReply ){
     fprintf(g.httpOut, "HTTP/1.0 %d %s\r\n", iReplyStatus, zReplyStatus);
     fprintf(g.httpOut, "Date: %s\r\n", cgi_rfc822_datestamp(time(0)));
     fprintf(g.httpOut, "Connection: close\r\n");
+    fprintf(g.httpOut, "X-UA-Compatible: IE=edge\r\n");
   }else{
     fprintf(g.httpOut, "Status: %d %s\r\n", iReplyStatus, zReplyStatus);
   }

   if( blob_size(&extraHeader)>0 ){

I tested it against IE11 on Windows 8.1 in "fossil server" mode only. It does indeed fix both problems I noticed with IE in "compatibility view" mode. (Broken CSS handling for the logo, as well as the WYSIWYG editor problem.)

You still get HTML1202 warnings in the developer console (F12), but this appears to be bogus:

   http://msdn.microsoft.com/en-us/library/ie/hh180764%28v=vs.85%29.aspx

I assume it also works in CGI and SCGI modes, but I did not test this.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to