Closed
Bug 558100
Opened 16 years ago
Closed 10 years ago
Firefox does not send keyboard events from Mac character viewer until after some normal keyboard input has occured
Categories
(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jmott, Unassigned)
Details
Attachments
(1 file)
|
1.44 KB,
application/x-shockwave-flash
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
On Firefox Mac, we are receiving characters from character palette by TSM event handler with kEventTextInputUnicodeForKeyEvent that is installed when flash component ( such as TextField ) get the focus.
However, if text field was empty ( in other words, when a key down event has never come ) , we cannot receive that characters for some reason, though it was installed rightly.
I have investigated the inside of Firefox to confirm why this is happening. And then I found that Firefox activates a TSM document after a key down event as below code. I think this code relates to this bug.
#Code From http://mxr.mozilla.org/mozilla1.9.2/source/widget/src/cocoa/nsChildView.mm#5272
5262 - (void)keyDown:(NSEvent*)theEvent
5263 {
5264 NS_OBJC_BEGIN_TRY_ABORT_BLOCK;
5265
5266 // If a plugin has the focus, we need to use an alternate method for
5267 // handling NSKeyDown and NSKeyUp events (otherwise Carbon-based IME won't
5268 // work in plugins like the Flash plugin). The same strategy is used by the
5269 // WebKit. See PluginKeyEventsHandler() and [ChildView processPluginKeyEvent:]
5270 // for more info.
5271 if (mGeckoChild && mIsPluginView) {
5272 [self activatePluginTSMDoc]; <-- here
Maybe we cannot receive the key event from character palette before Firefox's activation code.
Reproducible: Always
Steps to Reproduce:
0.Launch the Character Viewer (from the Languages and Text drop down)
1.Load fooAS3.swf
2.Click in the text field (do not type)
3.Double click a character in the Character Viewer
Actual Results:
Nothing happens
Expected Results:
Character inserted
If you type even one character first, Firefox sets up the TSM document that allows it to forward events from the Character Viewer
Comment 3•10 years ago
|
||
I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Updated•3 years ago
|
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•