Browser Modes(Standard or quiks) based on Doctype

Question

0.00/5 (No votes)

See more:

Hi,
If HTML page has multiple frames and each frames opens an HTML page and since each of this html pages has different Doctype, then how browser would decide the Mode.

My actual requirement is to keep my webpages in quirks mode but i have a frames where i make use to render third party UI controls which supports only Standard Modes. So i want to keep only that frame in a Std Mode(using <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">)

as per my testing so far, even after changing doctype to Std mode, it is still behaving as quirks mode. The parent frame is still kept with doctype use to support quirk mode.

Posted 11-Apr-13 4:47am

devcode007

Add a Solution

Comments

Prasad Khandekar 11-Apr-13 11:03am

Have you tried using <meta http-equiv="X-UA-Compatible" content="IE=Edge">. It will force browser to switch to Standard Mode.

devcode007 11-Apr-13 12:07pm

ok I will try this...meanwhile can you tell whether it switches to strict standard mode or Almost standard mode. I want browser to entertain legacy stuff as well as oppose to strict standard mode which i believe set things as per HTML5 strictly.

Prasad Khandekar 11-Apr-13 15:07pm

I think you are better of putting the meta tags in all your pages where Standard Mode is desired. More information about various modes is available here (http://www.nczonline.net/blog/2010/01/19/internet-explorer-8-document-and-browser-modes/)

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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