Hello Don
On 09-Jun-0, you wrote:
>
> Many thanks to Olli, Zapek, Matt and anyone else who did anything.
> You are doing a great job.
>
>
> Right button now works in Moobunny. Excellent.
>
>
> First bug reports:
>
> http://www.amiga.org/article.php?sid=992&mode=thread&order=0&thold=0
> Two JS errors
This is because amiga.org sucks.
> http://www.sonyclassical.co.uk
> menu at left not working, function problems
>
> http://www.sonyclassical.com
> recoverable alert
>
> http://www.sonyclassical.com/music/47298
> This page now displays, BUT click on the red box next to the envelope
> and Voyager crashes
I've looked at these sites before and can reproduce no crashes from
them - but then they DO use Flash and I *don't* have the Flash plugin
installed anymore (because sites like the lotr one below try to use
percentage widths, and because VFlash doesn't respond to it too well
when you resize the window, which I inevitably do)
> http://www.naxos.com
> moving mouse over menu of links at left gives "Invalid type conversion"
> errors
I have an idea what this is, and it's known.. V got some IE DOM compatibility
thrown in, which is bound to start to "break" on some sites (they'll use the
code:
<script>
if (document.all) // this must be IE4+
{
// mess with stylesheets
}
else if (document.getElementById) // this must be NS6 or IE5+ using W3C DOM1
{
// mess with stylesheets in a different way
}
// universally usable browser code like image rollovers
</script>
So it'll be trying to assign some value to something somewhere that
V doesn't fully support.
Basically this site is trying to use the stylesheet properties for
positioning and visibility, among other things, to create menus -
V does not support either the CSS that enables visibility, nor the
positioning, and obviously not the Javascript DOM stuff that
enables it to be dynamic.
The site is no less useful or more breaking than it was before, but
you may notice the errors a little more now than you would have.
I'd say, for sites like this, that you should ignore any errors until
the CSS is implemented that make them work..
> http://www.lordoftherings.net/index_flat.html
> This very difficult site is nearly working now. Layout on this page is
> not quite right, and various JS errors still come up such as "unknown
> opcode".
I mailed you PERSONALLY as to why this site doesn't work: Voyager has
a nasty bug whereby calling functions across framesets does not work:
essentially it starts executing random code. This is what the unknown
opcode thing is - but since it *is* random code, it also leads to a crapload
of crashes too. Randomly.
If you have a frames site with random nukes, THIS is almost certainly
what the problem is.
> http://www.polarne.co.uk/glass.html
> JS imagelinks not working
We did add <A onClick> but for some odd reason this site doesn't work
with them (and it's this site that we used as an impetus to get it in V, or
more precisely your whining about it, Don :)
If anyone has ANY clue as to why.. please say so :)
(someone was asking about some Cancer feature/survey earlier in the
month, I checked this site and it's fixed, sorry you couldn't do the survey
though)
> It would help if View Source had visual word wrap. The above page
> (probably done on a Mac) comes out as one enormous long line.
That's a bug. The site is nicely tabbed.. and I think that may be part
of the problem. It's a known bug, a bug which you have reported
before and we have said "we know, we have a list" about..
.. probably not a Voyager bug either, I don't see how V could be
reponsible for mangling the code (invoking an editor puts mangled
code in the editor, straight from the textinput gadget.. so I can
only assume this is some odd textinput problem)
> Why is getting Lists to work such a problem? (www.nordicglobal.com -
> news)
Because there are better, more interesting bugs to fix. There is no PROBLEM
with it (apart from the fact that lists are notoriously difficult to get to do
nested list layout, I think according to Olli) just things like crashes,
Javascript, site-breaking, show-stopping, world-ending bugs get fixed
first.
Would you rather have the .104 beta as stable as it is now, or for it to be
the prettiest crash-fest imaginable (like IBrowse, no less)?
Happier now, Don? :)
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
