Hi Matt,
On Tue, Dec 26, 2000, at 10:36 PM, you wrote:
>
> Hello Bob
>
> On 26-Dec-00, you wrote:
>
> >> What is griping going to do, though? I don't think I'd be so annoyed
> >> if any of the gripers had actually sent in a decent bugreport on WHY
> >> the JS engine isn't working at a certain site.
> >
> > Griping provides stress relief for the griper. Nothing more.
> >
> > Well, I for one remember being shot down by one Matt Sealey for
> > mentioning bugs found in one V 3.3.35 alpha.
>
> When they released 3.3.35 they said explicitly not to report bugs.
>
> Now they're asking for it to get the bugs fixed faster (in .35 half of
> the browser wasn't even there ;)
>
> > Voyager's JS because it crashes so hard.
>
> So use wget to download the source code, or view the site in
> Internet Explorer or IBrowse or AWeb..
>
> > non-critical failures like mouse-overs doing funny things that were
> > repeatable and evident, it would be a lot different than I ewnt to
> > url:x and the system gurued.on loading. We the users, haven't got a
> > clue as to what the JS engine barfed over.
>
> Surely you can do a little more than say "http://www.mysite.com
> doesn't work! It make crash my Amiga which perfect fine! And I
> think SHOULD fix now, buggy browser pay no I!" and so on..
>
> >> The JS problem ALSO isn't as simple as tweaking a line of code and
> >> having it all magically work as planned. As long as you just bleat out
> >> "it doesn't work at http://..." then stuff ain't gonna get fixed as
> >> fast as when you explain that navigator.mimeTypes[] isn't implemented
> >> and some MP3 site won't let me download a file because of it.. (not a
> >> real example)
> >
> > See my comments on the problem on finding what 1 line of 300 on a page
> > causes the system to crash.
>
> There are ways to debug a page you can't see, you just have to work
> them out. The more you learn, the cleverer you get :)
>
> Thanks
> --
> Matt Sealey <[EMAIL PROTECTED]>
> Website http://www.kittycat.co.uk
>
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.
Now, if you mean that, by looking at the URL history logue,
which V and all other browsers keep, will allow us to know what
caused the crash, the question is, "How?" Not all of us have suf-
ficient education, exposure and experience, with respect to js and
all, to know where to start looking for a clue. If you truly want
us to be able to give better bug reports and direct you to where
something *is* going wrong (other than just the URL), then, how
about supplying us with a tiny tutorial, here, one that we can all
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.
Anyway, thanks for listening.
Julian.
--------------------------------------------------------
Author of "MSH Tutorial V. 3.0". Found on Aminet -- MSHTut30.lha
Julian Aronowitz. Tel.: (718) 654-1681;
E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED]
_____________________________________________________________________
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
