- If you need to have an href link that actually has no destination, DO
normal web browsers this works perfectly. A few will complain that a return
has been used outside of a function
- FIX: Place a 'return false;' in the onClick method, and a dummy
URL in the href. The return false; will make sure the browser doesn't
actually go to the URL. Although just in case, using '#' as the URL
works well as a backup plan.
- If you are getting errors when submitting a form, of which a Java Applet
is being accessed to create part of the process ...
- FIX: Check the onLoad method on the page before allowing the
submit to happen. If the Java Applet hasn't loaded yet, you will get
some lovely JS errors.
- In Netscape 3.x, a call to document.write, if included in a table, will
sometimes fail to work. It never works in a nested table, and even in regular
tables will fail more than 50% of the time.
- FIX: Either stay away totally from using document.write in
tables, OR have the document.write CREATE the whole table itself.
will quickly find that Internet Explorer has a 'feature' built in to it.
You can only access public METHODS of the Java Applet from Jscript, not
the public variables as well. Whereas Netscape allows both public variables
and methods to be used.
- FIX: If you need to access a public variable of the Java Applet,
you will need to write a method into the applet that simply returns
the variables value
errors if you try to access this item named target - however as a form,
it will submit perfectly.
- FIX: Stay away from calling any form element 'target'
then it must in ALL CASES end with a return function or else any 68K Mac
(Or Netscape v3.0)
- FIX: ALWAYS if you return in one place, at least place a generic
return true; (or false) right before the function ends.
- ANNOYANCE: Netscape 4.x on a Mac (68k OR PPC) will sometimes decide
hit Reload - It works fine. But another page will do it again eventually.
- ANNOYANCE: Wierd characters on a Macintosh. Sometimes, Macintoshes
don't like &'d HTML special characters. More specifically, they don't
like them if the person resizes the window, or if the screen gets refreshed
(such as having too many tables, or graphics in tables without sizes.) When
the web page gets refreshed SOMETIMES those special characters (including
non-breaking space - *GRRR*) will turn into other, multinational-style,