search

Letractively / morisoliver

Automatically exported from code.google.com/p/morisoliver
0 stars 0 forks source link

Get out of Quirks Mode for IE #130

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It's better for feature compatibility not to be in Quirks Mode.

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 28 Feb 2012 at 6:45

GoogleCodeExporter commented 8 years ago

Original comment by Aleda.Fr...@state.ma.us on 20 Apr 2012 at 3:31

GoogleCodeExporter commented 8 years ago 
Aleda, if I add this line to the top of my local moris.php

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" 
"http://www.w3.org/TR/html4/strict.dtd">

everything works fine.

I vaguely recall having to make sure that line was NOT in any of the master 
PHP's, but perhaps the OL upgrade took care of this.  Could you verify?

More basically . . . isn't this what this issue is referring to?

Original comment by cpl...@gmail.com on 27 Oct 2012 at 7:26

GoogleCodeExporter commented 8 years ago

Original comment by cpl...@gmail.com on 31 Oct 2012 at 6:40

GoogleCodeExporter commented 8 years ago 
Note to self - In FF right click on page and choose "View Page Info" to see 
what mode

Original comment by Aleda.Fr...@state.ma.us on 31 Oct 2012 at 7:11

GoogleCodeExporter commented 8 years ago 
OK, now it says "Standards compliance mode" - CZM and I should test everything

Original comment by Aleda.Fr...@state.ma.us on 31 Oct 2012 at 7:14

GoogleCodeExporter commented 8 years ago 
Note to self - In IE click on the upper right gear tool, choose "F12 Developer 
Tools" and look at the "Document Mode" menu on the Developer tools window.

Original comment by Aleda.Fr...@state.ma.us on 1 Nov 2012 at 7:09

GoogleCodeExporter commented 8 years ago 
Note to self:
  * IE is stupid.
  * Simply refreshing a page after removing the DOCTYPE header will not cause its mode to change.
  * Erasing the cache and reloading the page will STILL not cause its mode to change.
  * Only after closing the browser and accessing the page (even w/o a cache cleansing) will the mode check itself.
  * IE is stupid.

Original comment by cpl...@gmail.com on 2 Nov 2012 at 3:48

GoogleCodeExporter commented 8 years ago 
It is our current version of extjs (3.3.1) that is causing the strict standard 
mode to complain.

extjs is currently at version 4, and one of the enhancements is that I research 
what it would take to upgrade to 4.  Version 4 works nicely in strict mode.

BUT . . .

extjs version 3.4.0 DOES seem to work fine in strict mode, and a minor release 
upgrade should probably not introduce any new issues.  So my vote for a course 
of action would be that you download version 3.4.0 and point your control PHP's 
to that version (and add the strict doctype).  There are three places in your 
PHP that will need to be repointed.

http://extjs.cachefly.net/ext-3.4.0.zip

Original comment by cpl...@gmail.com on 2 Nov 2012 at 4:11

GoogleCodeExporter commented 8 years ago

Original comment by Aleda.Fr...@state.ma.us on 2 Nov 2012 at 5:31

GoogleCodeExporter commented 8 years ago 
Yay!

Original comment by cpl...@gmail.com on 2 Nov 2012 at 7:21