Error: Could not convert JavaScript argument arg 2 [nsIWebBrowserPersist.saveURI] = NS_ERROR_XPC_BAD_CONVERT_JS Source file: chrome://communicator/content/contentAreaUtils.js Line: 448
Now that you are on 2.0 release, this error is now different? (Different error, different line: ?)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 Pinball Refspoof CopyURL+ FetchTextURL FlashGot NoScript BANK OF AMERICA.COM ONLINE BANKING SUCKS IN THE HUGEST WAY IMAGINABLE
I too am having the hanging download problem. This is the dialogue box I get when trying to 'Save Target As' from any download link - this one happens to be the roboform.xpi.
SeaMonkey 2.0, Windows XP Home (Desktop), Windows Vista Home Premium (Laptop)
Right. When I was looking before, there were a number of possible bugs that may cover this situation. That was one I had looked at. That's also why I inquired as to a revised error, because the particular code referenced from that earlier build is no longer found in contentAreaUtils.js.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 Pinball Refspoof CopyURL+ FetchTextURL FlashGot NoScript BANK OF AMERICA.COM ONLINE BANKING SUCKS IN THE HUGEST WAY IMAGINABLE
@therube I messed around with browser.download settings and may have found the cause and solution of the issue. Seems download doesn't start if the "Save as" window opens before the download starts. That can easily happen on my slow connection. When I increase the value of browser.download.saveLinkAsFilenameTimeout from default 1000 to 10000 download starts first, the file is stored and there is no error. So an easy fix of the bug seems to be to increase the default value.
I messed around with browser.download settings and may have found the cause and solution of the issue. Seems download doesn't start if the "Save as" window opens before the download starts. That can easily happen on my slow connection. When I increase the value of browser.download.saveLinkAsFilenameTimeout from default 1000 to 10000 download starts first, the file is stored and there is no error. So an easy fix of the bug seems to be to increase the default value.
I certainly don't have a slow connection (about 20 MB/s). For me it was sufficient to increase from 1000 to 2000 to download all previoulsy failed links. I didn't test with lower.
Do you know if increasing this value might have any negative effects?
fred6633 wrote:I certainly don't have a slow connection (about 20 MB/s). For me it was sufficient to increase from 1000 to 2000 to download all previoulsy failed links. I didn't test with lower.
Do you know if increasing this value might have any negative effects?
Fred
I don't think so. It was discussed to increase it for Fx (where it doesn't have the same impact as in SeaMonkey) up to 3000. The only reason to set it as low as possible is, that people don't think download has not started yet.