Bob and Angel,
I started using doctype because I was told that browser updates might not
use display features above the declared doctype. So I set the bar high and
started using a syntax checker. I used "transitional" hoping that would
give me a pass on useful deprecated syntax. For example, turning auto
complete off in a text field is not a "legal" attribute, but it darn well
should be!
Now I'm thinking set the bar low and deal with any display shortcomings on
a case by case basis.
For what it's worth, my version of Jmol.js shows only 7 Messages (Blue) in
my syntax checker. They are all double variable declarations in functions
which should not be fatal. The fatal problem re the high bar is buried in
my code. Who knows. Maybe my use of autocomplete off attribute finally blew
up. It could also be that MSIE 9 finally objected to the applet tag I use
for JME in the page. Setting the bar lower looks like a good plan for now.
Angel, I just thought of something. That yellow applet message could have
come from JME. It's sitting right there. It's just hidden!
Otis
--
Otis Rothenberger
Department of Chemistry
Illinois State University
Normal, IL 61790-4160
http://chemagic.org
----------------------------------------
From: "Robert Hanson" <[email protected]>
Sent: Friday, May 13, 2011 1:47 PM
To: [email protected], [email protected]
Subject: Re: [Jmol-users] MSIE 9
Your page looks fixed. I had copied the older version. Someone tell me why
it's important to include this doctype crap on a web page.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
