Hello Julian
On 27-Dec-00, you wrote:
> Not to seem pedantic, but, I *must* beg the question, already,
> asked, "How are we or can we determine what caused V to crash,
> while we were first entering a site, when that crash caused our
> Amiga to shut down (crash and guru)? How can going to that same
> site using AWeb, IBrowse, Netscape Nav/Comm, MS IE, tell us what
> caused V to crash and crash our computers?" The whole point being
> that the crash was sudden.
The easiest way is to stare at the code. You eventually get a taste for
good HTML and can spot it a mile off. The same goes for bad HTML -
it's plain to see that some freakish value or use of tag can throw a
browser off. Example, there is http://www.userfriendly.org, which
uses a table with a width of 3000 pixels for the top banner.
Obviously it would be NICE if you could see if there IS Javascript in
there, or whether the crash is purely layout related. Disabling JS
and then visiting the site off a fresh reboot might prove that too.
But the more the authors and designated testers have to repeat
those tasks to get a result that brings forth a fix, the less fixes
get done in the time.
In essence, V is buggy because you are lazy, if not stupid ;)
(no offense ;)
> keep on hand. I am not joking in this request. I know how busy
> you probably are, but, you seem to want our help and you are asking
> for some specifics.
Yes, as specific as you can get!
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
