| Quirks Mode or Standard Mode in RAP? [message #1692483] |
Thu, 16 April 2015 08:09  |
|
One of our customers noticed that RAP browser applications specify the following DOCTYPE:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">.
According to WIKI's definition (http://en.wikipedia.org/wiki/Quirks_mode) this will trigger Quirks mode in all modern browsers rather than Standard (CSS compliant) mode.
It probably isn't important, but I was interested in an explanation, what it means, and why RAP chooses to go with what appears to trigger Quirks mode?
Does this have a potential effect on the box model and images in terms of layout, or does RAP need this in order to get its size and layout calculations correct?
By the way, I'm using RAP 2.3... perhaps it is all changing in RAP 3.0?
Thanks, John
---
Just because you can doesn't mean you should
|
|
|
|
|
| Re: Quirks Mode or Standard Mode in RAP? [message #1693431 is a reply to message #1693083] |
Fri, 24 April 2015 08:36  |
|
Hi again Tim... our customer is asking for some more clarification on Quirks Mode in RAP, so wonder if you can provide some suitable responses...
Can you explain the relationship between the quirks doctype declaration and RAP's usage of http-equiv?
For instance:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title></title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="viewport" content="initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0" >
<!--- IE9 render in standard mode, all older versions in quirksmode --->
<meta http-equiv="X-UA-Compatible" content="IE=5,9,10,11;" >
As per https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx
Should meta http-equiv="X-UA-Compatible" content="IE=5,9,10,11;" take precedence over <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">? Would there be issues with iframe usage?
We seem to be defaulting to quirks document mode (when testing with IE11) despite content="IE=5,9,10,11" declared in the head. A few things I noticed in previous testing/investigation;
- Quirks mode is different within pre-IE 10 in comparison to anything IE10 and later.
- My understanding is quirks mode doesn't exist in Project Spartan which will likely ship with Windows 10. We want to be best positioned moving forward.
- Relying upon quirks mode for IE doesn't take advantage of IE11 'compliance' to standards. If we made changes to accommodate a quirks document mode, if we considered giving Chrome a try there would be issues whereas IE11/Chrome displayed nearly identical.
Thanks, John
---
Just because you can doesn't mean you should
|
|
|
| Re: Quirks Mode or Standard Mode in RAP? [message #1694576 is a reply to message #1693431] |
Wed, 06 May 2015 12:28 |
|
Any thoughts on the above response?
The concern is what happens when Quirks Mode is removed altogether in the browser, from IE12 (AKA Spartan) for example, and RAP stops working?
In IE11, Quirks Mode is considered deprecated already - it still works, but they say that you shouldn't use it (see the link in the previous post).
Can this be confirmed, or explained please?
Thanks, John
---
Just because you can doesn't mean you should
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03049 seconds
] 
Search
Help
Register
Login
Home
