« US government desktops | Main | CEO transition »
December 14, 2007
sIFR, Moviestar, more
sIFR, Moviestar, more: Last week Adobe Flash Player r115 went live to consumers. Today there's an update notice from the sIFR project, which puts display text for HTML pages in SWF files for better rendering. If you used a "hover color" in sIFR, then Moviestar breaks it, and you'll need to update sIFR. [via John Henshaw] In other compatibility notes, Rich Ziade noted some type of change in HTTP services, and the Adobe website itself was apparently tripped up by this technote, which doesn't differentiate between top-level domains and subdomains during getURL requests. One more thing to be aware of: this security article has the implied action item to test any pre-existing use of cross-domain policy files immediately, and if issues arise, to check against well-formedness of the policy file and against any intra-domain redirects to your policy file. I've held off on posting these alerts because I haven't been able to get confirmation from the team during recent large internal Adobe meetings, and because I was out-of-the-country during most of Moviestar beta and so am not sure what was already in public discussion and what was not. Anyway, if you use sIFR on any site, then please update it to accommodate the new Player, and please doublecheck any use of cross-domain policy files in the new Player too. My apologies for dropping the ball on highlighting these changes.
Posted by JohnDowdell at December 14, 2007 10:19 AM
Trackback Pings
TrackBack URL for this entry:
http://weblogs.macromedia.com/mtadmin/mt-tb.cgi/9183
Comments
Thanks John for the great info, that effects me.
Thanks
David
Posted by: David at December 14, 2007 11:22 AM
Hi John, thanks for spreading the word. I did not find that technote before, and although it explains changes related to the sIFR problem, it does not explain why getURL("asfunction no longer works. Could you provide insight on this?
(And yea, I realize using getURL to call an ActionScript method is silly, but that's how the code ended up.)
Posted by: Mark Wubben at December 15, 2007 02:12 AM
Hi Mark, thank for stopping by, and thanks again for the work you're doing with sIFR.
I've been out-of-the-loop with Moviestar changes. Did something change with asfunction too? If so, then we should have highlighted all these project-affecting changes in one place.
(Quick web searches on "adobe moviestar asfunction" don't reveal much, so it seems like there wasn't much conversation while I was on sabbatical. I've never liked that "asfunction" call; overloading getURL to ask the browser to process some ActionScript just seemed weird to me, so I've always kept it at arm's length. But we should still clearly warn if past behavior changed.)
Posted by: John Dowdell at December 15, 2007 07:26 AM
Yea, the getURL/asfunction broke, and by proxy sIFR did.
Posted by: Mark Wubben at December 15, 2007 11:05 AM