I actually deleted this post, I didn't want a bunch of flex fans to gang up on me.
I just hope the powers that be can read through the lines and see how frustrating this issue is. Everyday I defend the virtues of Flash. I have to tell you though, on this point, the naysayers of Flash that mutter bs like 'Flash isn't a proper development framework' score a point one for their side of court on this issue. I'll be a very happy person and do my victory dance when this issue if totally resolved and make sure that I point out to them this issue has been fixed. Danny, Thanks for asking the question, and please continue to ask... I am actually going to start pointing my frustration at the people who develop browsers too.. Thanks, Patrick --- In flexcoders@yahoogroups.com, DannyT <danmo...@...> wrote: > > I actually raised this at FOTB, whilst no one had a definitive answer it's > possible the cause of this stems from the Browser Plugin APIs available for > the Flash Player to leverage. FP relies on the browser for it's REST > implmentation (AIR offers full support apparently) and as such can only get > at what the plugin api offers. > > However, this isn't necessarily STILL the case but could have been in older > browsers. No one I spoke to had the answer for sure so I'd still be very > interested in a more precise explanation. > > 2009/9/29 djhatrick <djhatr...@...> > > > > > > > Sorry, I am tired to explaining why this doesn't work to our REST api > > programmers, and it's been years and still no solution.... It's so annoying, > > because it makes programming very difficult... Standards are out there for a > > reason! Will somebody raise their hand ask the teams why this still isn't > > addressed at adobe max next week for me, please? > > > > Maybe somebody at Adobe should get off their ass and prioritize this issue > > with browser vendors? > > > > Pissed and frustrated, again and again > > Patrick > > > > > > > > > > -- > http://danny-t.co.uk >
