Firefox fails to handle javascript:void(0) after ocr-url install
Things started with OCR urls. Everything had been working a few weeks ago, but now suddenly Firefox couldn't handle ocr addresses. They would direct me to a page that says: "The address wasn’t understood."
Simple solution for a Debian Linux user, just install ocr-url. I did this and ocr links work perfect, but now I'm getting the same error with javascript:void(0) links. That was quite unexpected. Perhaps I should have done some more investigating before installing ocr-url. Something else may have been wrong and the simple solution may have just covered it up, since that had been working before as well. The ocr links just didn't really raise a red flag as i hadn't tried to use one in a while, but I know javascript:void(0) links were working yesterday.
So now I can't use links in my Amazon account, or any other javascript:void(0) links. I can open Chrome, but it's just ugly and a pain to use on my Debian system. I would really like to get full functionality on Firefox back if anyone can help. Thanks.
In about:config I have the following: services.sync.prefs.sync.javascript.enabled;true javascript.enabled;true network.protocol-handler.external.javascript;true
I have tried in safe mode with same result. What should I look at next?
Giải pháp được chọn
No. That OCR program shouldn't have any effect unless this link is about that specific protocol.
Does this happen with all links that show javascript:void(0) on hover?
Did you make changes to other protocol prefs?
- network.protocol-handler.external.javascript
You can rename/remove prefs.js in the profile folder to see if that has effect.
You can create a new profile to test if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
Đọc câu trả lời này trong ngữ cảnh 👍 1Tất cả các câu trả lời (12)
Hi, separate Security Issue please uninstall Flash 22.0 r0 as per your Linux flavor suggests and install : Flash Player Version: 29.0.0.140 Current Version https://get.adobe.com/flashplayer/otherversions/ Step 1: Select Operating System Step 2: Select A Version (Firefox, . . . .) Note: Other software is offered in the download. <Windows Only>
I forgot to mention that the correct page actually displays for a split second before going to the error page, which seems strange.
Được chỉnh sửa bởi Velady vào
javascript:void(0) is a placeholder URL (href). The actual action is done via an onclick handler attached to the link. If the link isn't working then make sure that you aren't blocking such JavaScript links. The Inspector usually shows an 'ev' button at the end of such a link.
Note that you need to register a protocol to make such a link work.
Pkshadow. I tried what you suggested, but now javascript:void(0) links go directly to the error page instead of flashing the correct page first.
Sadly, javascript:void(0) links still aren't working. Thanks for the security issue tip, though.
Any other suggestions to try?
Được chỉnh sửa bởi Velady vào
Hello, Cor-el. I'm trying to figure out the parameters for registering the protocol. I see ev in the links as expected.
Sorry this has me so befuddled, but I think this might be the thing to solve it. I haven't done this before. I have allocated handlers for the browser by editing files, but that was a little different.
What exactly do I put in as the protocol and what command do I use? Then do I map it to the Flash Player I just installed?
- gconftool-2 -s /desktop/gnome/url-handlers/foo/command '/path/to/app %s' --type String
- gconftool-2 -s /desktop/gnome/url-handlers/foo/enabled --type Boolean true:
Được chỉnh sửa bởi Velady vào
Easiest to do this is to let Firefox handle this by creating an expose pref.
- network.protocol-handler.expose.foo (or ocr in your case)
OCR is working now. Are you suggesting the ocr-url program I installed is interfering with javascript:void(0)?
Giải pháp được chọn
No. That OCR program shouldn't have any effect unless this link is about that specific protocol.
Does this happen with all links that show javascript:void(0) on hover?
Did you make changes to other protocol prefs?
- network.protocol-handler.external.javascript
You can rename/remove prefs.js in the profile folder to see if that has effect.
You can create a new profile to test if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
Thank you, cor-el. Finding the boolean:
- network.protocol-handler.external.javascript
in about:config and setting it to false did the trick. It only does the trick for void(0) links, however, which was the only problem I had run across until I thought I had it fixed. Now there's another similar javascript problem. It appears it's not completely fixed.
Được chỉnh sửa bởi Velady vào
I seem to have run across another aspect of the same problem with Firefox not handling javascript correctly. I'm getting the same (javascript) error page with:
- network.protocol-handler.external.javascript;true
and absolutely nothing happens with;
- network.protocol-handler.external.javascript;false
I created network.protocol-handler.expose.javascript and get the dialog to choose an application, but I don't know what to map it to, or even if this is relevant.
So, I'm scratching my head again. It might take me a while to get to the prefs.js and creating a new profile. I have a lot of work to get through before tomorrow morning, which this has interfered with quite a bit. It looks like I'm stuck with Chrome until I can deal with this tomorrow evening.
Được chỉnh sửa bởi Velady vào
In the end I removed the prefs.js file. Something in it was not happy. Everything is working just as expected now. I forgot about that little file. It seems like flushing that file every once in a while fixes all the little problems. Thanks, cor-el.
Velady said
You can rename/remove prefs.js in the profile folder to see if that has effect.