User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6 Athough Ctrl-X strictly means cut, which you can't do from something read only like a web-page, conventionally in this situation much software just do a copy (Ctrl-C) instead. Browsers often do not, and it's absolutely maddening. Reproducible: Always Steps to Reproduce: 1. Select an area of any webpage 2. Do <Ctrl-X> 3. Paste into Notepad or wherever. Actual Results: What are pasted are the previous contents of the clipboard, whatever they were, not what was intended to be copied off the web page. Expected Results: Should have behaved like <Ctrl-C> and copied the selected contents, and subsequently pasted them.
Well, no, I think the current behavior is the correct one. All you need to do is copy, don't cut.
(In reply to comment #1) > Well, no, I think the current behavior is the correct one. All you need to do > is copy, don't cut. If it was as simple as that in reality, I wouldn't have bothered to file this, though I half expected simply to get a tart unhelpful reply. Thanks. The point is that the two keys are next to each other, and easy to mistake, if, as I do, you work a lot in the dark lit only by the screen. There really is no reason why on a read only document such as a webpage <Ctrl-X> shouldn't copy, so why not help your users?
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.