This is a migrated thread and some comments may be shown as answers.

Mega Menu messed up with IE compatibility mode.

1 Answer 43 Views
Menu
This is a migrated thread and some comments may be shown as answers.
Cory
Top achievements
Rank 1
Cory asked on 05 Jul 2016, 01:41 PM

I've attached a mega menu example in the pictures below where the only thing I changed between the "Good" and the "Bad" was the "Display Intranet Sites in Compatibility Mode".

Basically when compatibility mode gets in the way the display of the menu gets completely messed up.  Has anyone else had this problem / fixed it?  The menu is part of a master page - which seems to drive the problem somewhat too - the master page was the generated single menu one that Telerik supplies. 

The solution – according to the web – is to force IE to display using the latest engine (EDGE) by doing the following with the web.config:

<system.webServer>
    <httpProtocol>
      <customHeaders>
        <add name="X-UA-Compatible" value="IE=Edge" />
      </customHeaders>
    </httpProtocol>
</system.webServer>

Or you can do the following in each page:

<head>
   <meta http-equiv="X-UA-Compatible" content="IE=Edge" />
</head>

Unfortunately in the environment I'm in – neither of those solutions accomplishes the objective – the application stays in compatibility mode either way – at least when a master page is involved.

I've noticed that the radGrid gets messed up to - the columns don't resize correctly.  Plus the fonts get messed up somewhat when compatibility mode is engaged. 

 

HELP!!!

Thanks,
Cory Aston

 

1 Answer, 1 is accepted

Sort by
0
Marin Bratanov
Telerik team
answered on 05 Jul 2016, 02:08 PM

Hello Cory,

Indeed, this is the recommended solution because we do not support IE7 (and, hence, the Compatibility mode): http://www.telerik.com/aspnet-ajax/tech-sheets/browser-support.

If even adding the X-UA value as an HTTP header does not help, you can discuss the issue with the local administrators team so they can remove the checkbox via group policy).

I can also suggest that you compare the master page that causes the issues with another that doesn't to find the difference (e.g., invalid markup, another X-UA meta tag later in the head, the meta tag not being placed early enough).

Regards,

Marin Bratanov
Telerik by Progress
Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer and share your thoughts.
Tags
Menu
Asked by
Cory
Top achievements
Rank 1
Answers by
Marin Bratanov
Telerik team
Share this question
or