On Sep 13, 2005, at 5:42 , Bob Hanson wrote:
mayscript fails to validate in xhtml transitional, yes. it
still works, though, so when you say not allowed, I'm a bit
confused.
Not as confused as I am (obviously).
blind leading the blind? ;-)
...
> validation has nothing whatsoever to do with functionality of
your code
> in a browser. in a perfect world, all browsers would run only code
> that validates against the designated specs (determined by the
> doctype). this is not at all the case, though. :-(
Ah, that's a distinction I'm trying to learn about. validate vs.
allowed vs. works. Sounds familiar. I think I was hoping for more.
If my code doesn't validate -- as will result from "mayscript" --
then I just cross my fingers that browsers will still accept it --
that it won't knock out IE and that Netscape will be happy. Or that
Miguel can get Jmol.js to deliver an applet only when absolutely
necessary. Is that the idea? Should I not care? I'm not sure what
the point of moving toward valid XHTML code is if the applet code
itself won't always validate.
I think this is the reason for transitional doctypes. I use xhtml
transitional, and put things like the applet tag in my pages, and
they validate *and* work (except the mayscript attribute does not
validate).
I do not trust strict doctypes for the simple reason that I can not
name a browser that is fully compliant. I would love to write fully
validated code under a strict dtd, but not if it means it won't work,
obviously! :-)
I have this Mac/Safari LiveConnect failure in the back of my mind,
of course. I'll be running some tests tonight with the <object>
code Miguel has in Jmol.js. The documentation pop-up examples
should be delivering object code now. (You can tell if it is if the
pop-up reads "object applet" just under the applet frank.)
I keep trying object in place of applet, and keep returning to
applet. I'll be interested to hear how your tests work out, if you
don't mind posting...
Maybe it's too much to ask that switching to <object> will fix
that. But the fact that Nick reported this in the NEWEST Mac OS
suggests MAYBE? the problem is with the <applet> code itself. I'm
crossing my fingers that Miguel's object fix will fix the Mac
LiveConnect bug.... Hey, I'm an optimist! :)
do you use a strict dtd? that's the only reason I can see for the
applet tag failing (related to dtd, that is).
tim
--
Timothy Driscoll
molvisions - see. grasp. learn.
<http://www.molvisions.com/>
earth:usa:virginia:blacksburg
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
