|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When trying to submit my first contribution, the file Browse button
works once then after a file is selected it disappears. And the file
that was chosen doesn't appear on the screen.
I'm using Netscape 7.0.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Leroy Whetstone" <lrw### [at] joplincom> wrote in message
news:48A### [at] joplincom...
> When trying to submit my first contribution, the file Browse button works
> once then after a file is selected it disappears. And the file that was
> chosen doesn't appear on the screen.
> I'm using Netscape 7.0.
>
I don't have Netscape installed, but I have Firefox which I think should be
the same code base and I submitted stuff just a couple of hours ago.
Have you tried coming out of the browser, logging on again and trying the
same thing again? It might also be worth trying to clear the cache before
trying again on the remote off-chance that the Javascript file in your cache
didn't come down correctly.
If it does the same thing consistently then it may take a little bit of
debugging.
The page uses Javascript when you hit the Browse button to hide that Browse
button and create a new one so that you can submit an unconstrained number
of files on the one form. It sounds like the Javascript is running
(otherwise the button wouldn't dissappear). It must be running into problems
before creating the new one. I don't think Netscape automatically displays
Javascript errors, but it should have an option to view the error console
(probably an option on the tools menu). To get a clean view of the problem
you can 'clear' the panel, refresh the page and repeat the Browse operation.
If that reveals a problem can you post what it says here.
Thanks,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris B wrote:
>
> I don't have Netscape installed, but I have Firefox which I think should
> be the same code base and I submitted stuff just a couple of hours ago.
> Have you tried coming out of the browser, logging on again and trying
> the same thing again? It might also be worth trying to clear the cache
> before trying again on the remote off-chance that the Javascript file in
> your cache didn't come down correctly.
>
> If it does the same thing consistently then it may take a little bit of
> debugging.
>
> The page uses Javascript when you hit the Browse button to hide that
> Browse button and create a new one so that you can submit an
> unconstrained number of files on the one form. It sounds like the
> Javascript is running (otherwise the button wouldn't dissappear). It
> must be running into problems before creating the new one. I don't think
> Netscape automatically displays Javascript errors, but it should have an
> option to view the error console (probably an option on the tools menu).
> To get a clean view of the problem you can 'clear' the panel, refresh
> the page and repeat the Browse operation. If that reveals a problem can
> you post what it says here.
>
> Thanks,
> Chris B.
I found the javascript error code(it was where ya thought) it's:
Error: uncaught exception: [Exception... "Index or size is negative or
greater than the allowed amount" code: "1" nsresult: "0x80530001
(NS_ERROR_DOM_INDEX_SIZE_ERR)" location:
"http://lib.povray.org/js/submission.js Line: 984"]
I also tried the suggestions you gave to solve the problem, but nothing
worked. Could my java be bad? I did have a 'melt down' a while back that
killed a lot of files, so much so that I reboot win98.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Leroy Whetstone" <lrw### [at] joplincom> wrote in message
news:48A### [at] joplincom...
> I found the javascript error code(it was where ya thought) it's:
>
> Error: uncaught exception: [Exception... "Index or size is negative or
> greater than the allowed amount" code: "1" nsresult: "0x80530001
> (NS_ERROR_DOM_INDEX_SIZE_ERR)" location:
> "http://lib.povray.org/js/submission.js Line: 984"]
Ah! On a positive note, Netscape seems to give good error messages. On a
less positive note this seems to be a bug in NS7.
The Javascript line it's complaining about (984) inserts a new row into the
table that contains the list of files. This line does indeed use a negative
index (-1) which should insert the new row at the end of the table.
Unfortunately, on Googling this issue, I see that Netscape 7 had a bug
dating back to 2002 and didn't handle this as it should do to be compliant
with the DOM standards. Netscape apparently agreed to fix this, and if they
did so then subsequent versions of Netscape shouldn't suffer from this
problem.
I see that Netscape got up to Version 9 before AOL pulled the plug. You can
download a newer version from http://browser.netscape.com/releases if you
want to try that. Otherwise I can confirm that neither IE 7 nor Firefox 2
suffer from this bug.
Not an ideal answer I know, but the only work-around I spotted so far would
mean making quite significant changes to that section of code (which took
quite some time to get working in the first place).
Regards,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris B wrote:
> Ah! On a positive note, Netscape seems to give good error messages. On a
> less positive note this seems to be a bug in NS7.
>
> The Javascript line it's complaining about (984) inserts a new row into
> the table that contains the list of files. This line does indeed use a
> negative index (-1) which should insert the new row at the end of the
> table. Unfortunately, on Googling this issue, I see that Netscape 7 had
> a bug dating back to 2002 and didn't handle this as it should do to be
> compliant with the DOM standards. Netscape apparently agreed to fix
> this, and if they did so then subsequent versions of Netscape shouldn't
> suffer from this problem.
>
> I see that Netscape got up to Version 9 before AOL pulled the plug. You
> can download a newer version from http://browser.netscape.com/releases
> if you want to try that. Otherwise I can confirm that neither IE 7 nor
> Firefox 2 suffer from this bug.
>
> Not an ideal answer I know, but the only work-around I spotted so far
> would mean making quite significant changes to that section of code
> (which took quite some time to get working in the first place).
>
> Regards,
> Chris B.
Thanks for all your help!
I had Netscape version 9 before my melt down. Lost it. I guess it's time
I reloaded it.
Thanks again!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |