Some of the webpages I visit have stubborn save file dialogs for executables. I would like to do one of the following using an extension:
Save the file by default and close the dialog box. I looked at http://kb.mozillazine.org/File_types_and_download_actions It doesn't really work for these files (the problem is described at: http://kb.mozillazine.org/File_types_and_download_actions under 'Unable to set automatic action. I verified the headers.)
I guess I can use browser.download.manager.closeWhenDone from https:// developer.mozilla.org/en/Download_Manager_preferences , if I figure out the first part :)
Suppress the download manager from showing any such dialogs altogether.
I found https:// developer.mozilla.org/en/nsIDownloadManager#addListener() and https:// developer.mozilla.org/en/Download_Manager_improvements_in_Firefox_3 that look promising. I don't really know how to extract the source URI for the transfer either. I'm curious if anyone has any existing examples for using these or if there's a better way to do this. Or if someone knows what part of Firefox's code I could poke, that would be useful too.
Thanks!
PS: Sorry,I had to break the hyper-links above with an unnecessary space after https:// - apparently I need 10 reputation to do that :)
FWIW, I managed to work around this - though my solution probably wont work for most others.
Fortunately I'm behind a proxy I control, so I just corrected the obnoxious headers (Content-Disposition and Content-Type) before they reached Firefox. These were forcing Firefox to open the File Save Dialog box despite my specified preference to 'Always save file of this type'. Furthermore, I set 'browser.download.manager.closeWhenDone' property to True. Works for me, and I cruise through such sites w.o being interrupted.
Related
I don't get how this thing is so buggy on my mac ugh
Firstly it is such a hassle to open cuz it won't open in chrome without typing in the IP manually (is there still no solution besides changing settings that won't work)??
But most importantly, my CSS file is just not loading...
I did everything already from restart to reinstall, etc.
And when I open the file from Chrome the code does works so it's not my link...
Does anyone have another solution for the CSS to load, please?
To give some feedback (after a LOT of crying and tinkering around)...
I think fixed the CSS file not loading on Live Server? It seems that the extension loads the resources as if the folder the HTML is in is the root, so I had to use a relative path (which took a WHILE to get to its liking as well...)
Still not opening without a fuss though haha...
I am not aware that I changed (not even saved it differently) anything in the workflow, but the content of all containers changed to "Delegate: Body" (see picture):
The Robot works, nevertheless it is not so confortable because also preview pictures disapear, in Selector is only the window for text and I cannot validate it.
Does anyone have an idea how to turn it back?
Edit: there is result of search for packages:
This is due to the fact that the designers didn't load. It's most likely a bug. Does it happen even if you close and re-open the project?
Firefox is misbehaving, so I was looking around in about:config, and I stumbled upon something that looks like code. It was in a config variable called extentions.5103ad57a64ad.scode. I'm not familiar with the environment in which this code might run, and it seems to me that it is somewhat obfuscated, but I figure there must be someone here who can figure it out.
For readability, I've put in newlines after most semicolons, and in a few other places; originally, the code was all in one long line.
I'm having trouble with pasting the code and getting the formatting right, so I've uploaded the code to Dropbox here https://dl.dropboxusercontent.com/u/86984895/ff_code.txt
Since my first guess is that the code is malicious, I cleared the variable. It has since reset itself. I do have an idea of how to clean my machine of any malware I may have caught, but I'm still interested in knowing what this code would do, if it were run.
Seems like you have the IETab plus addon installed, which installs adware. When you go to a google page this addon shows price comparison information.
You should uninstall IE Tab Plus and install IE Tab 2, found here:
https://addons.mozilla.org/en-US/firefox/addon/92382/
Or, if you can, don't install IE Tab at all.
Hoping someone can provide an answer with this, although it's not 100% programming related. All of a sudden my IIS6 install on Server 2003 will give me a "404 Not Found" error when I try to load any file ending in .asp.
I can see the file there if I turn on directory browsing, but clicking on it immediately gives me a 404. Regular HTML pages load just fine, it's only the ASP files that it cannot find, although they're right in the directory alongside the HTML file.
I'm probably forgetting something stupid - can someone remind me what I need to do in order to get it to load properly?
In the Web Service Extensions area, make sure Active Server Pages is enabled
We ran into this issue of late. Besides the Web service extensions where one enables asp, there is another place in each site that needs to be checked.
Virtual directory:
In IIS 6.0, open the properties of the virtual directory. Navigate to virtual directory tab - at the bottom, click on configuration - make sure that the .asp extension is in that list. If it's not, you can find the dll somewhere like this path: C:\WINDOWS\system32\inetsrv\asp.dll. Also, the verbs will need to be added on this same window. The main choices are GET, HEAD, POST (and maybe TRACE if need be).
Web site
In IIS 6.0, open the properties of the site. Navigate to Home DIrectory tab - at the bottom, click on configuration - make sure that the .asp extension is in that list. If it's not, you can find the dll somewhere like this path: C:\WINDOWS\system32\inetsrv\asp.dll. Also, the verbs will need to be added on this same window. The main choices are GET, HEAD, POST (and maybe TRACE if need be).
I hope that helps - I didn't find this mentioned after a fairly extensive search.
Duh - I knew it was something stupid that I just overlooked (shows how often I use Classic ASP). Thanks a bunch.
I am working on a new version of a firefox extension, but after releasing it, and incrementing the em:version in install.rdf and update.rdf, when I click "Find updates" Firefox reports that "No updates were found." When I run it with debugging on, the output in the console is actually identical to what I see when I don't put the update live.
It starts with RDFItemUpdater:checkForUpdates with all of the parameters, and returns with Addon Update Ended and status: 8.
I verified with McCoy tool that the extension is signed, and has the same Id as the old one, etc. I'm not sure what else to try. Any advice would be appreciated. This is with Firefox 3 (and the extension is marked as compatible with it... that didn't change).
Make sure your update.rdf file is being served with an appropriate Content-Type, i.e. text/rdf, text/xml or application/xml+rdf
If you've only recently changed update.rdf, maybe it's cached. Load it in the browser then Shift-Refresh.
here are some nice tips that helped me: https://developer.mozilla.org/en/Extension_Versioning,_Update_and_Compatibility
but, auto update function will not work if extension is marked "experimental".
I'm having a similar issue, and think it's due to an invalid rdf file. Did you check that yours parsed with this tool? http://www.w3.org/RDF/Validator/
There are lots of things to mess up, one of which is installing an extension from AMO and expecting it to update when you change your update.rdf :)
I was having the same problem. In my update.rdf, I had a wildcard in my minVersion attribute:
minVersion="3.0.*"
Removing the wildcard fixed the status 8:
minVersion="3.0"
The update works now (console shows status 1). This was using Firefox 3.0.18.
My guess is that status 8 means there was a problem understanding the contents of the file (not necessarily an RDF parsing problem). If your minVersion doesn't have a wildcard, maybe there's an invalid character hiding somewhere.