Hello Ingo
On 27-Jan-01, you wrote:
>
> [...]
>
>> 3.3.71
>> ------
>> - JS: fixed a rather nasty bug that JS execution context
>> (variables etc.) got mixed up between frame sets when JS
>> code was executed in various frames at the same time (Olli)
>
> Great. This really gives me hope that I can use my strictly HTML4.01 &
> JS1.2 Homepage with Voyager again. The "reload frameset when user directly
> loads frame" functionality was always missing a variable defined in
> another frame.
It certainly doesn't complain now, but I do see a problem in that when I
click the buttons, it loads the page into the right hand frame, then
reloads the frameset again, resetting the right hand frame to the title
page.
What EXACTLY is it INTENDED to do? It'd be nice to know what you mean
it to do, and whether V is strictly doing that..
> If the MouseOver effect does work /in a frame/, too, I'm rather happy.
> I give you cheers when this happens. You might check this (and not be
> bored by faulty code causing these effects) on my homepage (see below).
The "Aqua" buttons onMouseOver nicely now.
Thanks
--
Matt Sealey <[EMAIL PROTECTED]>
Website http://www.kittycat.co.uk
_____________________________________________________________________
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
