Dear Adobe,
I am a Flash developer. I do a lot of work in Flash Professional, Flash Catalyst, and the Flex framework via Flash Builder. Working in Flex, of course, makes having the debug version of Flash Player on my systems a simple job requirement. However, I am also a web user – like most geeks (and these days, really like most people in general) I do spend a fair amount of time just surfing the web. Recently, those two activities have come into conflict, though, because surfing the web with the debug version of Flash Player – especially on Firefox – has become annoying at best, and downright infuriating at worst. I know I am not alone here, either, and I have seen others comment on Twitter about their frustrations of trying to be a web user while having the Flash Player debugger installed. I am not one who is generally inclined to just complain about things without at least trying to do something about it, so I have outlined below three things that I believe can be done to fix this problem.
First, why is the debugger installed with Flash Builder, but not Flash Professional? Ultimately, the problem I and others have is that too many Flash designers publish movies with errors in them. To a point, you can almost argue that it is not entirely their fault, since the “normal” version of Flash Player is designed to fail silently, so many of these designers may be entirely unaware that their movie is generating errors. In fact, just today I reported a Flash error to a very large, quite prominent blog, and got a quick response back that they could see no errors when they loaded their page. And of course not: they have the normal version of Flash player. I forwarded them a screenshot of their page with the error displayed, but obviously it would have been better if they had known about it in the first place. So my first suggestion is this: get the debugger out to folks using Flash Pro. Push an update to Flash Pro that installs the debugger, and moving forward, make sure that whenever someone installs Flash Pro, they also end up installing the debugger (just as now happens when one installs Flash Builder). That way, all of those folks out there that are building Flash content in Flash Pro will be able to see and fix their errors before they publish.
Second, please provide a way for those of us running the debugger to turn it off. I absolutely need it in order to build my apps, and I absolutely do not need it in order to just surf the web. I’ll be the first to admit that I do not know exactly how plug-ins work, so this might be more difficult than it sounds. However, I would really love to be able to tell Flash Player that, for this browser session, I don’t need debugging, thank you very much. Even more ideally: allow me to disable debugging by default, and only turn it on when I actually need it. That way, for that majority of the time when I’m using my browser as, you know, a browser, I could actually use it and not spend so much time wondering why so many people publish Flash content with errors (although, see above). When I needed to get some work done, though, I could enable debugging and thus make it so that I did not become one of those folks.
Third, and this is really the most important piece: please fix the debugger for Firefox. It is simply broken. When I hit a page that contains Flash errors in IE, I get the error dialog box, click Dismiss, repeat for each other error, and then continue surfing. On Firefox, however, I get the error dialog, and then the browser locks up. I cannot click the Dismiss button; instead, I just get the little spinning circle. Thankfully, I have learned that I do not need to kill Firefox entirely: I can instead press Ctrl-Shift-Esc and simply kill the plugin-container.exe process. Of course, if I want to then view Flash content, I have to restart the browser. What is even more fun is when the error dialog box pops up but then immediately loses focus and drops down behind the browser window so that it cannot be seen, leading me to think that the browser itself has in fact crashed. Again, none of these problems are present on other browsers, so clearly there is just something wrong with the Firefox plug-in. By the way: I am seeing these issues on Firefox 3.6.13 on 64-bit Windows 7 Home Premium, running the debug version of Flash Player 10.1.
Thank you.
Sincerely,
Rob
(Note to my users: constructive feedback is welcomed in the comments. Generic “I hate Flash” or “Flash sux” comments will be deleted.)


