I can no longer automatically capture source URL in ClipCache Pro.
I've been a registered user ClipCache Pro since 1998, using Firefox at least that long. CC is a Windows clipboard monitor/database, storing captured data until I delete. When capturing almost anything from FF, I would also capture the source URL, in addition to several other columns of info.
After a recent FF upgrade (don't remember exactly which one), the source URL capture no longer functions. Visiting the same website and capturing the same date in MSIE does also capture the source URL. Just installed FF 64-bit, but that didn't solve the problem.
I've looked at FF settings and about:config, and searched the 'net, but no answers found.
I may install Opera if I can't get FF working correctly again.
I've attached a screenshot; the relevant column is highlighted. It shows how it's supposed to work, how FF is no longer doing this but MSIE is. --> after more than 5 min, the JPEG won't upload, so no attachment.
Any help would be appreciated.
--Just_George
被采纳的解决方案
Try to disable multi-process windows in Firefox to see if that has effect.
You can disable multi-process windows in Firefox by setting these prefs to false on the about:config page.
- browser.tabs.remote.autostart = false
- browser.tabs.remote.autostart.2 = false
You can open the about:config page: via the location/address bar. You can accept the warning and click "I'll be careful" to continue.
定位到答案原位置 👍 2所有回复 (4)
选择的解决方案
Try to disable multi-process windows in Firefox to see if that has effect.
You can disable multi-process windows in Firefox by setting these prefs to false on the about:config page.
- browser.tabs.remote.autostart = false
- browser.tabs.remote.autostart.2 = false
You can open the about:config page: via the location/address bar. You can accept the warning and click "I'll be careful" to continue.
THANK YOU!
autostart.2 was set to true. Now set to false. Tested on several different websites, all is working the way it should.
I wonder what changed it from false to true about 2 months ago. That may have been when I added Privacy Badger to FF. I don't know what else I would have done that would cause that to happen, but now I know how to fix it.
Thank you again, cor-el, and for the speedy response.
--Just_George
It was false in the past because the Firefox developer hadn't finished multi-process (e10s; Electrolysis) at that time. It got enabled a few versions back (possibly 48), but still may not work stable enough in a lot of cases.
When multi-process is enabled the content process runs in a sandbox that can't be accessed by external software.
Thank you, again, cor-el. Informative, simple, and (almost) understandable for someone like me <vbg> .
--Just_George
由Just_George于修改