So this means holding back a better user-experience only because Adobe and other plugin-writers are lazy? Or because there are a couple of old flash-apps which 'might' use keyboard-shortcuts they shouldn't have used at all? Now that's for a strange, user-unfriendly decision. Take a look at the discussion, the number of votes on this bug. Marking this as WONTFIX equals WEDONTCAREABOUTUSERS imhoe. If this is the state Mozilla is in, it's a sad day for me.
(In reply to LAFK from comment #630) > Mozilla took different approach to Chrome - Chrome decided to take back > keyboard, FF doesn't want to harm Flash plug-ins that might be using it. > That is also why Roth's patch was rejected. > > When Flash adopts the NPAPI proposal and makes necessary changes, so will > Mozilla. No sooner will this be fixed than that, because otherwise it's hard > to test. > I recommend closing this / marking as "won't fix" with appropriate comment > "waiting for Adobe". > > If someone has information why the approach "not to take back keyboard > unless Flash allows us to" was chosen, please share. I'd say it's wrong > approach, but my perspective is personal, and perhaps there are facts > speaking in favour for plug-ins. > > PS. A bit of irony: under the window I'm writing this in, there's "Status: > NEW". :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263435 Title: Firefox cannot close tab (using Ctrl-w) when flash content is selected on page To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
