Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
See more: .NET2.0 ASP.NET HTML
Is there any way to force IE10 to render the website in compatibility mode using some meta tag ? Thanks.
Posted 11-Mar-13 8:06am
Comments
Sergey Alexandrovich Kryukov at 11-Mar-13 13:08pm
   
It's hard to say if this is a good idea or not. Web pages are not supposed to be contaminated with IE-specific content...
—SA
learner'sbug at 11-Mar-13 13:12pm
   
I understand but our clients only use IE so that won't be an issue.
Marco Bertschi at 11-Mar-13 14:34pm
   
Maybe it will be. The problem is not the IE as a browser, it is the compability mode. You'd better update the stuff that it is good formatted in the normal IE mode.
learner'sbug at 11-Mar-13 14:52pm
   
Thanks for the reply. I am looking into that option now as it seems that as a developer you don't have control over compatibility view and it is handled by a compatibility view list by Microsoft.
Marco Bertschi at 11-Mar-13 15:03pm
   
Yeah - And even the compability view is changed with every version of internet explorer.
Therefore it is the best to keep your app up to date with the current and the last two versions of IE (I assume none of your clients is using IE 6, 7 or older? If they'd do you may want to point out the hazard for their IT infrastructure this might cause).
Sergey Alexandrovich Kryukov at 11-Mar-13 18:59pm
   
Agree.
—SA
Sergey Alexandrovich Kryukov at 11-Mar-13 18:59pm
   
Who can force anyone to use only IE? No, it will be an issue...
—SA
Marco Bertschi at 12-Mar-13 2:19am
   
It is IMO only an issue when you force your customer to use the compa mode of IE. In addition the maintainability of the aapp goes below zero when explicitly working with the compa mode (which is just a workaround for above stated situations).
If the customer comes and says "You don't need to make it browser independent, we use IE anyways" (Which is actually the case in my current comapany) it is just a legitimate use case. Off course - a customer will pay more if he suddenly wants to have FF or Chrome enabled for the app - But even then it is another use case.
 
-- MB
Sergey Alexandrovich Kryukov at 12-Mar-13 2:36am
   
It is not a legitimate case. Here, there is no such thing as customer. A person talking to you is some representative who usually have no idea what customers really want. Do you want to make evil even to one customer? Fortunately, this case is relatively easy: tolerance to different incompatibilities is achieved through the simplicity of design (I don't say the simplicity is easy though).
—SA
learner'sbug at 12-Mar-13 16:08pm
   
Actually its the same case in our company as customer don't want to pay for FF , Chrome compatibility but completely agree that there is no excuse for using compatibility mode though.

1 solution

Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

As a conclusion of the above posted comments:
 
The problem is not the IE as a browser, it is the compability mode. You'd better update the stuff that it is good formatted in the normal IE view.
Even the compability view is changed with every version of internet explorer. Therefore it is the best to keep your app up to date with the current and the last two versions of IE (I assume none of your clients is using IE 6, 7 or older? If they'd do you may want to point out the hazard for their IT infrastructure this might cause).
The compability view is just a tool from MS to keep web sites which were created by lazy web-devs and have not received an update for a few years alive.
If you are changing something on your website look that it will run without the compability mode - it will extend the life span of your app.
 

cheers,
Marco Bertschi
  Permalink  
Comments
Sergey Alexandrovich Kryukov at 11-Mar-13 19:00pm
   
Agree, a 5.
—SA

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 OriginalGriff 190
1 Jochen Arndt 165
2 PIEBALDconsult 150
3 BillWoodruff 148
4 DamithSL 140
0 OriginalGriff 5,695
1 DamithSL 4,591
2 Maciej Los 4,012
3 Kornfeld Eliyahu Peter 3,480
4 Sergey Alexandrovich Kryukov 3,190


Advertise | Privacy | Mobile
Web01 | 2.8.141220.1 | Last Updated 11 Mar 2013
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100