Closed
Bug 308703
Opened 19 years ago
Closed 17 years ago
No Flash Asian/Japanese IME input on OS X Mozilla if move focus outside app and back. Mozilla Type-And-Find bug: "Find stopped", "link not found"
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: aliuson, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: When inputting Japanese IME in Flash input textfield then move focus outside of the browser window then back, you can no longer input text. Reproducible: Always Steps to Reproduce: 1. Open up a Flash movie in Mozilla that includes an input textfield. 2. Input some Japanese text using the IME 3. Click on the desktop/finder. 4. Click back into the Flash input text field. 5. Try to type Japanese Actual Results: No text is accepted (no floating input window comes up). I can see the characters in the center of the Mozilla bottom vertical bar (the characters appear in Japanese). When I hit enter, as I would do to tranfer the chars from a regular IME to Flash, that Mozilla bar says, "Find stopped." Or, it says "Link not found: "j character here"". Expected Results: Floating window comes up, receives chars, and chars get into text field accurately. Regarding this, Peter L. at Netscape says, "Sounds like a focus issue. Try clicking in the form field again to make Flash active. When you get the "link not found" or "Find stopped" message, that's our Type-And-Find feature which finds and highlights hyperlinks in the page based on what you type when the document has focus." Unfortunately, no amount of re-clicking on the Flash content makes this Type- And-Find go away. I must click on the browser window outside the Flash content, and then return to the Flash content. The problem is that Mozilla is not giving Flash keyDowns in this case.
Comment 3•17 years ago
|
||
(1.5 years later) No reply from reporter, which did not even wrote which product/version he was using. (Would have been "Incomplete", now is) R.Invalid
You need to log in
before you can comment on or make changes to this bug.
Description
•