Closed
Bug 166955
Opened 24 years ago
Closed 24 years ago
type ahead find causes typing failure in mail compose window after returning from browser
Categories
(SeaMonkey :: Find In Page, defect, P1)
SeaMonkey
Find In Page
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.2alpha
People
(Reporter: myk, Assigned: aaronlev)
References
Details
Attachments
(1 file)
|
580 bytes,
patch
|
bzbarsky
:
review+
dbaron
:
superreview+
|
Details | Diff | Splinter Review |
Every other time you return to a mail compose window from a browser window, type
ahead find is enabled in the mail compose window, causing you not to be able to
type additional alphanumeric characters into your message.
Steps to Reproduce:
1. Start composing a new message.
2. Go to a browser window.
3. Return to the message compose window.
4. Type more alphanumeric characters.
5. If your characters appear, repeat steps 2, 3, and 4.
Expected Results: your characters appear.
Actual Results: your characters do not appear, and on Windows the type ahead
find bell rings (saying it can't find the characters you type)
Additional Information:
Reproduced on Linux and Windows 2002-09-05.
ok. the following keys work:
'"/`
<enter><tab><space><backspace><delete><right><left><up><down>
the following don't work:
{}|:<>?~[]\;,.-=_+
numbers, letters, shifted numbers, shifted letters
additional information: reported to aaronl earlier this week.
oh and of course if typeahead find is found to be the cause then I consider this
a blocker for typeaheadfind to be included in the installer builds for 1.2a.
| Assignee | ||
Updated•24 years ago
|
Blocks: isearch
Severity: normal → critical
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla1.2alpha
| Assignee | ||
Comment 2•24 years ago
|
||
Seeking r=/sr=/a=
Comment on attachment 98045 [details] [diff] [review]
Argh - I was setting mFocusedWindow in the wrong place, it was only getting set when typeaheadfind was *not* allowed in the window
sr=dbaron
Attachment #98045 -
Flags: superreview+
Comment 4•24 years ago
|
||
Comment on attachment 98045 [details] [diff] [review]
Argh - I was setting mFocusedWindow in the wrong place, it was only getting set when typeaheadfind was *not* allowed in the window
r=bzbarsky
Attachment #98045 -
Flags: review+
| Assignee | ||
Comment 5•24 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 6•24 years ago
|
||
Asa gave a= on IRC.
Updated•18 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•