Opened 4 years ago

Last modified 4 years ago

#292 new Adopter Support

IE hates NJSHAD

Reported by: Maria Baron Owned by: Maria
Priority: Unknown Milestone: Adopter Support
Component: View-App Version: 2.2
Severity: Unknown Keywords: browser, IE
Cc:

Description

NJ's query looks really weird and mostly doesn't work in IE (v10 or v11). It had been working but I must've made a change along the way that IE doesn't like. Everything looks good and works properly in Chrome, Firefox, and Safari.

Attachments (1)

IE ugliness.pdf (206.1 KB) - added by Maria Baron 4 years ago.
This is what query builder looks like in IE.

Download all attachments as: .zip

Change History (2)

Changed 4 years ago by Maria Baron

Attachment: IE ugliness.pdf added

This is what query builder looks like in IE.

comment:1 Changed 4 years ago by Paul Leo

Later version of IBIS require more recent versions of IE

IE has compatibility emulation modes. These are used to make older sites display better in newer versions of IE.

You may check what version IE11 is emulating by clicking on the gear in the upper right corner of IE, and selecting F12 Developer tools, then selecting emulation and examining the Document mode. There may also be an information icon which will will give the mechanism of how the mode has been set.

Compatibility modes may be set in many ways.

https://msdn.microsoft.com/en-us/library/jj676914(v=vs.85).aspx

Describes the ways compatibility modes may be set.

If you examine the compatibility settings in IE by clicking on the gear in the upper right corner of IE, and selecting Compatibility settings, there are 2 checkboxes labeled:

"Display Intranet sites in Compatibility View"

"Use Microsoft compatibility lists"

These checkboxes may be controlled by IE group policy objects, see http://blogs.msdn.com/b/ie/archive/2008/10/02/ie8-group-policy.aspx

On Maria's desktop the "Display Intranet sites in Compatibility View" is checked, and cannot be unchecked. When she views the IE emulation, I believe it is set for IE7

Maria could try to have IT change that group policy

On my desktop which is not in NJ intranet, I had the "Use Microsoft compatibility lists" checked. MS compatibility lists are maintained by MS, and updated automatically, see https://msdn.microsoft.com/en-us/library/gg622935(v=vs.85).aspx which also describes how to update the list

The IE emulation mode was set to IE9, which should be fine for ibis, but I'm not sure the lists are actually working correctly. There was an entry in the MS compatibility view list for state.nj.us, but it was not for NJSHAD, yet still my browser was set to IE9 emulation mode.

You may be able to see the list here, but it may eventually be a stale link, as these get updated: https://iecvlist.microsoft.com/IE11/1387494476607/iecompatviewlist.xml[[BR]]

Maria could put a note on the welcome page to inform uses to uncheck either box if they are able to, and also try to get the list "fixed".

None of the above solutions seem satisfactory.

https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx

Describes how to set meta tags to control the document modes (compatibility settings)

This tag:

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

places Internet Explorer into the highest supported document mode (this is equivalent to setting the doctype, but that has already been set in the xslt template, and is being overidden)

We are experimenting with adding that tag to each page by copying the following template from xslt/html/page.xslt to xslt/html/SiteSpecific.xslt in the main xslt directory and adding the above tag so the template will look like this

<xsl:template name="Page.head" ibis:doc="Produces the HTML HEAD element and contents.">

<head>

<!-- set by xsl output META http-equiv="Content-Type" content="text/html; charset=iso-8859-1" --> <!-- meta http-equiv="Content-Style-Type; charset=ISO-8859-1" content="text/css"/ --> <meta http-equiv="x-ua-compatible" content="IE=edge" /> <meta http-equiv="Content-Language" content="en"/> <meta http-equiv="Content-Style-Type" content="text/css"/> <meta http-equiv="Content-Script-Type" content="text/javascript"/> <meta http-equiv="Reply-to" content="{$Page.ibisphWebmasterEmailAddress}"/>

<meta name="author" content="{$Page.metaAuthor}"/> <meta name="description" content="{$Page.metaDescription}"/> <meta name="keywords" content="{$Page.metaKeywords}"/> <meta name="robots" content="ALL"/> <meta name="google-site-verification" content="ZpJR4xS-qSQgDb1YulUQM83Nh0j6LzXwEChMX75GZiU" /> <!-- to use Google Webmaster tools 3/4/15 MLB -->

<title><xsl:value-of select="if(contains($Page.pageTitle, $Page.applicationTitle))then $Page.pageTitle else concat($Page.applicationTitle, ' - ', $Page.pageTitle)"/></title>

<link rel="shortcut icon" href="{$ibis.urlPrefix}image/application.ico" type="image/vnd.microsoft.icon"/> <link rel="icon" href="{$ibis.urlPrefix}image/application.ico" type="image/vnd.microsoft.icon"/> <link rel="home" href="{$ibis.urlPrefix}"/> <link rel="help" href="{$ibis.urlPrefix}home/Help.html"/> <link rel="toc" href="{$ibis.urlPrefix}home/SiteMap.html"/> <link rel="make" href="http://www.ibisph.org"/>

<xsl:call-template name="Page.standardCSS"/> <xsl:call-template name="Page.specificCSS"/> <xsl:call-template name="Page.printCSS"/>

<xsl:call-template name="Page.standardScript"/> <xsl:call-template name="Page.specificScript"/>

<xsl:call-template name="Page.otherHeadContent"/>

</head>

</xsl:template>

Maria will test in her dev environment, and depending upon outcome try in the production enviroment.

In my dev environment, checking emulation mode shows that it is set to Edge, and that it is done via an X UA comptible meta tag, the tag I placed in Sitespecific.xslt

Last edited 4 years ago by Paul Leo (previous) (diff)
Note: See TracTickets for help on using tickets.