Closed Bug 571537 Opened 15 years ago Closed 14 years ago

Flash 10.1 doesn't accept text input with Cocoa events

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
All
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking2.0 betaN+)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
blocking2.0 --- betaN+

People

(Reporter: BenWa, Unassigned)

References

Details

(Whiteboard: [Input])

STR: 1. Run the following game: http://www.kongregate.com/games/IriySoft/cursed-treasure-dont-touch-my-gems. 2. After the pre-loader, hit play. 3. In main menu select 'New game'. 4. Input name. Flash is not responding to keyboard input.
This bug isn't caused by the OOPP changes but it will impact the OOPP beta so I'm adding it to the tracker bug.
Blocks: 567265
blocking2.0: --- → ?
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a6pre) Gecko/20100613 Minefield/3.7a6pre Able to reproduce. When selecting "New Game" from main menu and trying to input Name, flash is not responding to the keyboard input.
Build worked : Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20090826 Minefield/3.7a1pre http://hg.mozilla.org/mozilla-central/rev/485a319ce5e6 Build broken : Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20090827 Minefield/3.7a1pre http://hg.mozilla.org/mozilla-central/rev/72d25f49cbcb Pushlog : http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=485a319ce5e6&tochange=72d25f49cbcb
The events appear to be implemented correctly part of bug 435041. We are investigating if Flash is responding to cocoa key events correctly or not.
Summary: Flash doesn't accept text input with Cocoa events → Flash 10.1 doesn't accept text input with Cocoa events
Flags: in-litmus?
Unfortunately this affects some Facebook games such as Pet Society.
I've seen this in a number of cases recently, too. Surely this must be a final-version blocker?
blocking2.0: ? → final+
Assignee: nobody → b56girard
I believe this bug also happens on YouTube. You can't pause any video with the space bar. If you play the video in full screen keyboard input works however. Could be related to bug 557225 as I didn't see this before that one landed.
The problem is not the same as bug 557225. The reason input handling does not work is because Flash is not responding to cocoa key event delivered via the NPAPI (Plug-in API). When entering full-screen mode flash creates a full-screen windows and does it own event handling.
We should fix this sooner rather than later as this causes people to switch browsers without hesitation.
Go to grooveshark.com and try to login. At least a couple of people have pinged me about this, and they report they can't enter text in other sites (that use Flash). I will re-request blocking2.0, so it gets triaged and, maybe, fixed earlier than final.
blocking2.0: final+ → ?
blocking2.0: ? → betaN+
This is caused by a bug in Flash 10.1, not Gecko, we're working on a resolution.
Josh, do you think we have everything we need to actually get to some sort of resolution? Do we need help from Adobe?
I've been talking to Adobe about this, I'll have an update soon.
We're seeing this quite a bit from our beta users via Input: http://input.mozilla.com/en-US/search/?q=flash+text+input&product=firefox
Whiteboard: [Input]
Assignee: b56girard → nobody
Component: Plug-ins → Flash (Adobe)
Product: Core → Plugins
QA Contact: plugins → adobe-flash
Version: Trunk → 10.x
Hardware: x86 → All
What's the plan for resolving this? ISTR it being deemed a bug with Flash 10.1, but I think this is also clearly a Fx4 final release blocker -- we can't ship if Flash doesn't work, no matter whose fault the root bug may be.
Component: Flash (Adobe) → Plug-ins
Product: Plugins → Core
QA Contact: adobe-flash → plugins
Version: 10.x → Trunk
Moving this back to Core so the blocking flag is visible and correct.
I'm checking on an update from the Flash Player side.
We have fixed this Flash Player bug internally and the fixed version of the player will be released within the next couple weeks of August. Thanks for bringing this issue to our attention.
Can we just make the blocking flag available for plugin bugs? I agree that we want this to be blocking but categorizing it incorrectly in order to make that happen isn't ideal.
(In reply to comment #25) > Can we just make the blocking flag available for plugin bugs? I agree that we > want this to be blocking but categorizing it incorrectly in order to make that > happen isn't ideal. Bug 584632.
I think the just-release Flash 10.1.82.76 fixes this. If someone else can confirm we can close this out.
Running 10.1.82.76, the original STR I posted are working.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Depends on: 589670
https://litmus.mozilla.org/show_test.cgi?id=12784 added to Litmus.
Flags: in-litmus? → in-litmus+
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.