Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

ClipCache no longer captures source URL in FF version 67

  • 2 antwurd
  • 1 hat dit probleem
  • 8 werjeftes
  • Lêste antwurd fan Just_George

Just_George
Just_George
more options

ClipCache is an extended clipboard manager for Windows, in use since 1998. I previously had this problem with FF in May 2017, and the solution from Mozilla Support was to disable multi-process windows in Firefox by setting the following prefs to false on the about:config page: 

   browser.tabs.remote.autostart = false
   browser.tabs.remote.autostart.2 = false

autostart.2 had been set to true, changing it to false solved the problem. That did not solve the problem with today's upgrade to FF 67.

Again, any help would be greatly appreciated.

ClipCache is an extended clipboard manager for Windows, in use since 1998. I previously had this problem with FF in May 2017, and the solution from Mozilla Support was to disable multi-process windows in Firefox by setting the following prefs to false on the about:config page: browser.tabs.remote.autostart = false browser.tabs.remote.autostart.2 = false autostart.2 had been set to true, changing it to false solved the problem. That did not solve the problem with today's upgrade to FF 67. Again, any help would be greatly appreciated.

Alle antwurden (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

browser.tabs.remote.autostart.2 hasn't been supported for quite some time and you can reset this via the right-click context menu to the default value because it won't have effect. Setting browser.tabs.remote.autostart = false should be sufficient to disable multi-process. You can check this on the "Help -> Troubleshooting Information" (about:support) page. If that doesn't help then the extension in likely broken with multi-process disabled as well.

You can check the Browser Console for messages related to this extension.

Just_George
Just_George Fraacheigener
more options

Thanks for the reply, but this didn't help.

ClipCache Pro (and BookMark Buddy) are not extensions, but are standalone programs. So my best uneducated guess is that those programs aren't broken.. As I said, they both worked perfectly up until v66.0.5. And they both work normally with Internet Explorer. And have used both since before FF was released.

I've downloaded FF v66.0.5 and will re-install that. And may give another look at Opera Portable.

I looked at Web Developer as well as refreshed the browser, neither helped.

Again, thanks for the feedback.