Closed
Bug 275797
Opened 20 years ago
Closed 19 years ago
Highlighted text in any input field does not get picked by PGP shortcut keys
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: pavel.penaz, Assigned: bugzilla)
Details
I am not sure how to describe this bug the best, it occurs every time and is not present in IE 6.0. Steps to reproduce 1. Login to your Gmail account 2. Go to 'compose message' page 3. Write some text in the message area and highlight it 4. Set PGP 8.1 to default shortcuts (encrypt is by default CTRL-SHIFT-E) 5. Press the shortcut What really happens: PGP dehighlights the text and highlights everything else around the originally highlighted text, and only then encryption is applied. This way completely different text is encrypted. What should happen: PGP should apply encryption on the highlighted text. This works in IE.
Comment 1•20 years ago
|
||
Worksforme, 1.0 and 20041223 trunk. No good ideas about why it doesn't work for you, though.
| Reporter | ||
Comment 2•20 years ago
|
||
Strange, I've just found this bug affects any text in any input text field. Step to reproduce: 1. Go to http://www.google.com 2. Write a search query 3. Highlight the text you wrote in the input field 4. Press the PGP shortcut See what happens.. I tried this with a new profile. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041223 Firefox/1.0+
| Reporter | ||
Comment 3•20 years ago
|
||
Affects branch as well here..
Comment 4•20 years ago
|
||
Could not reproduce on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041224 Firefox/1.0+
| Reporter | ||
Updated•20 years ago
|
Summary: Highlighted text in GMail compose window does not get picked by PGP shortcuts → Highlighted text in any input field does not get picked by PGP shortcut keys
| Reporter | ||
Comment 5•20 years ago
|
||
Still the same problem after clean install of WinXP Pro SP2 and with PGP Desktop 9.0 beta. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050311 Firefox/1.0+
Comment 6•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 7•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•