Closed Bug 293126 Opened 20 years ago Closed 19 years ago

shortcut of menu ineffective when my chinese input is on(I turned it to english text input status,I think other input program do occur this in Mozilla)

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: spectertech, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

when my chinese input IME is on, of couse I switch it to english text input 
status, then open my context menu, the shortcut keys of the menu r ineffective!
And when I use IME to enter some character in some the edit box in the page, 
the annoying find text show my inputs! actually these things should not be 
sent to mozilla till IME process these english texts to special characters 
like chinese or japanese

Reproducible: Always

Steps to Reproduce:
1.turn some language input on, such as IME, microsoft intelligent pinyin input
2.switch them to english text input status,
3.they can't work properly with mozilla's context menu shortcut keys.

1.input some random chinese or japanese characters in edit box, the annoying 
find text in link will show out when u typing the english texts which is still 
in the inputting stage not transform to chinese & japanese.

Actual Results:  
I think the most probable reason of thess phenomenum is that mozilla use some 
special key capture technology instead of use of the microsoft API.

Expected Results:  
I think the most probable reason of thess phenomenum is that mozilla use some 
special key capture technology instead of use of the microsoft API. I hope 
when transplant mozilla , the wisest thing to do is use the original microsoft 
APIs, you don't know what people use other languages & use other key related 
tools would cause.
Version: unspecified → 1.7 Branch
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/
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.