搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Clipboard manager issues with Firefox 44

  • 2 个回答
  • 5 人有此问题
  • 7 次查看
  • 最后回复者为 itdcmy

more options

I use a clipboard manager as a productivity aid, and it automatically keeps a history of all my copys and cuts. Since upgrading to FF 44, when I take a copy (or cut) of text, it no longer appears in the clipboard manager. It still works as expected in all other browsers and applications. A quick downgrade test found this feature working again. The same thing happens on another machine as well. I'm currently running Windows 7 Pro, FF 44.0.2 and the clipboard manager is Clipcache 2.9. Clipcache has worked well for me from XP through to Windows 10.

Anyone any ideas about this please?

Is it possible this is connected with the drag & drop from Keepass which also stopped working in the FF 44 upgrade? If so will the fix for that due in FF 45 also fix this issue?

I use a clipboard manager as a productivity aid, and it automatically keeps a history of all my copys and cuts. Since upgrading to FF 44, when I take a copy (or cut) of text, it no longer appears in the clipboard manager. It still works as expected in all other browsers and applications. A quick downgrade test found this feature working again. The same thing happens on another machine as well. I'm currently running Windows 7 Pro, FF 44.0.2 and the clipboard manager is Clipcache 2.9. Clipcache has worked well for me from XP through to Windows 10. Anyone any ideas about this please? Is it possible this is connected with the drag & drop from Keepass which also stopped working in the FF 44 upgrade? If so will the fix for that due in FF 45 also fix this issue?

被采纳的解决方案

hi, you could test if the clipboard issue goes away as well in firefox 45 beta which can be installed from www.mozilla.org/beta ...

定位到答案原位置 👍 1

所有回复 (2)

more options

选择的解决方案

hi, you could test if the clipboard issue goes away as well in firefox 45 beta which can be installed from www.mozilla.org/beta ...

more options

Many thanks Philipp for the prompt response. The answer is yes the next version has cured the issue.

Thanks for the help, much appreciated.