You can vote on what gets fixed in Flex, Flash, and Flash Builder

I’ve been working on a demo application to show off a new feature in AIR, and this sort of work has me interacting with the Adobe bug databases quite often. One of the things you may not realize is that the public has read and write access to the Flash Player, Flex SDK and Flash Builder bug databases; more than that, every submitted bug is read by Adobe employees at bug review meetings, and bugs that have more votes are recognized as being important to the community.

Here are some pending issues in the bug database that I care about. If you also want these bugs fixed, you should vote on them (or submit some of your own):

Flash Player:
“Allow fullscreen mode to stay active on one monitor while the user is working on another”
I’ve seen users of MLB.TV find the current behavior especially annoying: Flash Player will close full screen mode if you interact with another monitor.
https://bugs.adobe.com/jira/browse/FP-1723

Flex SDK:
“Clicking and holding on a DropDownList doesn’t select an item”
This affects all the drop down lists you see in Flex applications. When you click and hold a drop down list and let go of the mouse button when you’re over an item, the item isn’t selected and the menu doesn’t close. This is different than the behavior of native drop down lists in OS X, Windows XP, and Linux.
https://bugs.adobe.com/jira/browse/SDK-22208

Flash Builder:
“Cannot view any key bindings in General/Keys in Preferences with the Emacs scheme”
Despite using vi for text editing, I’m addicted to the Emacs key bindings Ctrl + a, Ctrl + e, etc. Flash Builder (quite coolly) has Emacs keyboard shortcuts built in, but this bug prevents the preferences window from showing all the shortcuts.
https://bugs.adobe.com/jira/browse/FB-21871

You have to register to vote or comment on a bug, but the process is standard and quick. Here’s the sign-up page: https://bugs.adobe.com/jira/secure/Signup!default.jspa

You can create your own bugs, and Adobe employees will read every one. You can do that here: https://bugs.adobe.com/jira/secure/CreateIssue!default.jspa
and you can search for existing bugs here: https://bugs.adobe.com/jira/secure/IssueNavigator.jspa.

4 Responses to You can vote on what gets fixed in Flex, Flash, and Flash Builder

  1. Radley says:

    This is (yet another) great way to reach out to programmers who use Flash. Unfortunately, a significant portion of Flash users come from a multimedia and/or design background and have no experience with JIRA.Any chance you’ll reach out the them?

  2. supra shoes says:

    I must to say this is a greatly article……..

  3. JabbyPanda says:

    SDK-22208 bug got a recent comment from Flex SDK engineer Deepa Subramaniam that “The behavior in the Halo CB and Spark CB will be identical”.Adobe is not going to fix this issue, the burden of this issue is placed on our developer’s sholders

  4. Reality says:

    Radley, I can’t imagine what you’d mean by reaching out to Flash developers for bug tracking with something other than JIRA. “Flash development” is not just “multimedia and design” anymore (and hasn’t been for many years), and Flash people are going to have to live with that and either expand their skill set to at least basic programming or be willing to work with someone who has that skill set.