"WaltS48" <thali...@REMOVEaim.om> wrote in message
news:8dWdnXv_fq3rQCTL...@mozilla.org...
> On 02/09/2016 05:58 AM, HoneyBun wrote:
>> If I highlight a URL in the navigation pane of Firefox 44, then
>> rightclick, it offers the usual Copy operation. However it won't Paste
>> directly into a text database such as MS Works. I must Paste it into
>> something else first, like Notepad, then it will Copy/Paste from there.
>> Weird.
>>
>
> Are you sure it isn't the MS Works-last released in 2007-that is the
> problem?
>
>> I blame Firefox. Typing a URL into the navigation pane sometimes hangs
>> for a second or two between keystrokes because it has become a
>> super resource & memory hog. It is often sucking off 95%+ of processor
>> time and 350+MB RAM.
>>
>> I've tried turning off the new push operation in Firefox 44, as well as
>> running it in safe mode (all add-ons disabled). No effect. It isn't
>> related to the number of open tabs, same problem with just 1 tab open.
>> Also this is a fairly new, clean install of Firefox.
>>
>> The above problems happen with a non-SSE2 processor and 1 GB RAM (the
>> max) on Windows XP. Yes, I know it's over the hill, but it's still a
>> good workhorse for me.
Yes, I'm sure Firefox is the culprit.
The same thing happens whether I'm highlighting and trying to copy text from
the body of a website, or the URL from the navigation pane. It won't paste
into MS Works. I must paste into something else first, such as Notepad, then
it will Copy/Paste into MS Works from there.
Problem discovered with Firefox 44 and MS Works 7 on XP.
Exactly same problem with Firefox 44 and MS Work 9 on W8.1.
No problems with IE8 and MS Works 7 on XP.
No problems with Chrome34 and MS Works 7 on XP.
No problems with IE11 with MS Works 9 on W8.1.
I don't have an older version of Firefox available to test, but suspect the
problem starts in recent versions (probably 40+).
Recent versions of Firefox are screwing up the basic Copy & Paste operations
of Windows via the clipboard, no doubt whatsoever.
Or I suppose we could call it an incompatibility between Firefox and MS
Works. I hope others running MS Works will confirm. Those running other
databases might also try it and report back.
No, I won't bother to try to report it as a bug to Mozilla. How could I
argue that it's important to keep Firefox compatible with MS Works which was
deserted by MS years ago, yet many such as I still use it? The Mozilla bug
reporting process is a nightmare anyway. I only know enough to stay far far
far away! :)
But maybe someone should let them know(?).
I've done all I can, and intend to do, hereby.
I'll simply use a different browser when MS Works is involved.