I was super excited yesterday when I started playing with FABridge and saw how great it worked. Fast forward to this morning when we moved the code and swf into the deployed .ASPX page and everything broke. Turns out this is a well documented (by users, not Adobe/MM) bug with ExternalInterface (which FABridge uses) when the swf is located inside a form tag.
In addition to various other scenarios where putting your swf inside a form tag is desired, its pretty much unavoidable on an ASPX page. Will this bug get fixed? I have seen some workaround code but this seems like something that is worth officially fixing. As it stands now it smacks of incompleteness and yet another scenario where .NET developers are seemingly ignored by Adobe. Thanks, Ben
