Hi Wouter,
Before I start, I'd better say I know nothing significant about JS, so
this message is very much from a "layman's" POV..
> > It surely supports onMouseOver and onMouseOut. I just used it
> > change graphics when the mouse it place above the button. It
> > was supposed
> > to change the status line too, but apparently Voyager won't
> > do both.
> I assume you mean 'link' when you say 'button'? A 'button' should sup
> port
I think the point was that, whatever the technical terms are, V does
react to OnMouseOver type events when relating to graphics. ISTR Neil
Bothwick's WireNet site exhibits both this and modification of the
status line. (Uffe? I'm sure I've seen V modify the status line and a
graphic??)
> I wrote the page according to Netscape's JavaScript standard. And it
> works
> in AWeb as well as in Netscape Navigator and Internet Explorer, so I
> would
> guess that the problem is not in my test page, but that the JavaScrip
> t
> commands like the ones shown above do not work in Voyager.
I just loaded the page up in Internet Explorer *4* and got two error
reports: document.img.onError not an object, and same for onLoad.
If the Vapor ppl say V doesn't do JS with Forms, I'd guess this means
it doesn't like the checkbox indicators. Although it may be more work,
you may get more realistic results having graphical indicators.
> 1. The table formatting clearly implies that the first big list of
[....]
Clearly you're pretty up to speed with JS. It is good that you have
taken the time to provide the resource, but it would be more useful if
it were less strict, or gave a broader picture of compatibilty. From
what I can tell of the Voyager version history, many of the problems
with JS implementation are with things breaking due to the way people
make it until it works with IE and NS, *not* according to the rules.
Providing compatibilty to broken code can break compatibilty with
correct code. :(
> 3. And I noticed the event names in the vapor page are without capita
> ls (so
> 'onmouseover' instead of 'onMouseOver', something they seem to find
> important in the standard, since it seems to have changed over differ
> ent
> JavaScript versions. It also says 'ondbclick' instead of 'ondblclick'
> , which
> I find rather discouraging.
Typos? Generalisation? I wouldn't put too much weight on those issues.
If you could provide a good resource to give many indicators of JS
performance under various contexts, it would be very useful to observe
the development of the features. And perhaps we non JS-literate ppl
might learn what the significance of some of those events really are! :)
Regards,
Ian
===
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
