Just a quick tip in case you missed it. I’ve written previously on how to better develop Flash and Flex on Google Chrome. But, since Chrome is now auto updating the Flash Player with the latest release version, it ignores other players, debug player included. In order to be »
I find Google Chrome fast startup and multiple processes, a key when developing Flash/Flex applications. And it’s my preferred target browser for stuff other than HTML. The problem is that, when debugging a Flash/Flex application and hitting a breakpoint, the Flash Player is stalled, chrome detect this »
This is by no mean a full technical comparison between these technologies, just a chat between 2 geeks. One is a skeptic backend dude 😉 and the other one is yours truly, a GUI guy. It started with an email from Eli (the backend dude) titled “the Next big thing”? Eli: »
Update: Added a sterilized demo and the source code. CSRF (Cross Site Request Forgery) is considered one of the most widely spread exploits in websites today. I’ve written before about how a legitimate Flash file (swf) can be extremely viral. Few days ago I did a real attack, exploiting »
Update: I’ve posted a real world example of this bug being exploited. This one has the same behavior on IE6, IE7 and IE8 betas. I have only tested this with Flash swf files, but it’s likely that this security is applied and broken the same way, when navigating »