IE10 with OTRS 3.0.7

[meukmans]

Hi,

With the launch of IE10 for Windows 7 I expect a lot of our customers to upgrade their IE version to 10.

Unfortunately we are still using OTRS 3.0.7 and after a quick test I don't seem to be able to type any text in the note part in OTRS (the complete field is greyed out). This is for both the client as for the user interface.

Is there any solution for this beside upgrading our OTRS version ?

[jojo]

use Chrome or Firefox

[meukmans]

I've thought about that but forcing the customers to install firefox or chrome just to use our helpdesk system is a bit too much I think..

[jojo]

Well Upgrade to OTRS 3.2 (which requires IE7 for customers at least)

[davidcatfnp]

Well Upgrade to OTRS 3.2 (which requires IE7 for customers at least)

Does this version fix the IE10 issue?
I am having the same issue


I currently running Internet Explorer 10 and have OTRS v 3.0.9
I get the following problem (see attached)

Capture.PNG

Everything else in OTRS works but the Text field doesnt, the drop down boxes work but appear in the wrong place.

Capture2.PNG

This work in IE9 but not IE10.
I am wondering if there is a simple fix for this (IE Setting/Page or File modifications on OTRS Server) or if we have to upgrade the version of OTRS.

[jojo]

IE10 is not supported by the CK Editor version used in 3.0

[davidcatfnp]

IE10 is not supported by the CK Editor version used in 3.0

Will it work if we upgrade to a later version?
Fo you mknow what particular version that IE10 support was added?
Or it doesnt work at all?

[jojo]

3.2.x works with IE10

[gears]

Using OTRS 3.0.11 - I found that the forms on customer + agent side would render correctly in IE10 by bringing up the IE10 ‘developer tools’ with F12 key and then select ‘Internet Explorer 7 Standards’ for the document mode. Forms were also at least "functional" with ‘IE8 Standards’ or ‘IE9 Standards’ but the rendering wasn’t perfect. I then applied info from http://msdn.microsoft.com/en-us/library ... 85%29.aspx to get the site code to force IE browsers into the IE7 mode -

Understanding legacy document modes

When using the X-UA-Compatible header to restrict a webpage to a legacy document mode, use one of the following values:

A value corresponding to a specific document mode, such as IE9 mode, IE8 Standards mode, or IE7 Standards mode. To do so, use one of the following declarations:

<meta http-equiv="x-ua-compatible" content="IE=9" >
<meta http-equiv="x-ua-compatible" content="IE=8" >
<meta http-equiv="x-ua-compatible" content="IE=7" >
By using one of these values, you're restricting the webpage to the standards mode of the corresponding version of Internet Explorer.

In certain cases, you might want Internet Explorer to use the document type declaration to either restrict a webpage to a specific standards mode or to use a document mode representing a much older version of the browser, such as Internet Explorer 5.5.

To do so, specify one of the following values, depending on your desired standards mode:

<meta http-equiv="x-ua-compatible" content="IE=EmulateIE9" >
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE8" >
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE7" >

(This setting is useful in cases where you might have a collection of webpages that use different values for the doctype directive.)

With these settings, the page is displayed either in the standards mode corresponding to the version you specified or it's displayed in IE5 (Quirks) mode.

For testing purposes, you can also use the following value to display the webpage in the highest standards mode supported by Internet Explorer.

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

Note Edge mode is intended for testing purposes only; do not use it in a production environment.

Because it forces all pages to be opened in standards mode, regardless of the version of Internet Explorer, you might be tempted to use this for all pages viewed with Internet Explorer. Don't do this, as the X-UA-Compatible header is only supported starting with Windows Internet Explorer 8.

Tip If you want all supported versions of Internet Explorer to open your pages in standards mode, use the HTML5 document type declaration, as shown in the earlier example.

The need to restrict a webpage to a legacy document mode usually occurs because the webpage is designed to support a given version of a browser or relies on older features that are no longer supported by the browser. Use legacy document modes only temporarily to allow your pages to be viewed while you update those pages to support current standards and practices.

If you decide to specify the document mode for a webpage, do so deliberately, for example:

Test the webpage in as many versions of Internet Explorer as you can, including new versions as they are released.
Set the content value of the X-UA-Compatible header to reflect the specific versions of Internet Explorer supported by your webpage, for example, the ones you've tested.
Don't set the content value to support versions of Internet Explorer that you haven't specifically tested with your webpage.

If you don't have time or resources to perform this testing, avoid setting the document mode. Only set the document mode when you have a specific business reason to do so. For more info, see When to use legacy document modes.
Determining document compatibility mode

To determine the document mode of a webpage while viewing it, use the F12 tools, as shown in Investigating document mode issues.

these changes have fixed the forms problem though I can't say for sure yet whether there could be other undesirable side effects. it seems OK so far:

/opt/otrs/Kernel/Output/HTML/Standard/CustomerHeader.dtl:
before: <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
after: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7,chrome=1" />


/opt/otrs/Kernel/Output/HTML/Standard/HTMLHead.dtl:
before: <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
after: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7,chrome=1" />