Take a look at this video. That’s why our web app still uses frames. I’m impressed by the efforts of those who attempt to make this work (Judah, et. al.), but I’m getting too old for hacks. Hacks are for AJAX developers ;). I want stuff to work out of the box. Apollo gets it right, so I’ll keep working on my Apollo app until the Flash player has WebKit built in (Flash 14?).
I wish that the Flash player supported modules that could extend its functionality. The core player would still be small, but sites that required additional functionality (like HTML rendering, or screen sharing) could require the installation of an additional module. I’m not suggesting third-party modules — only Adobe modules. There just needs to be some solutions so that we don’t have to hack this stuff up anymore. I’m preparing another post on why this is so important.
May 22nd, 2007 at 12:03 am
you just happened to pick the one browser I hadn’t tested with.. yet.
I *need* a HTMLControl component. I can’t come up with a decent work-around for what I need to do.
thanx for ruining my day!
(Ok, so it’s not your fault…)
May 22nd, 2007 at 12:20 am
Barry, I feel your pain
Sorry to ruin your day!
May 22nd, 2007 at 12:24 am
Hmm, I like the module approach, I think Adobe has plans to use something like this when rolling out versions of Apollo. ie. you go to download an Apollo app the requires a new version of the run-time so it downloads and installs the run-time as well.
Since we have Express Install already why couldn’t the module(s) download before the first swf that loads or as part of it?
Jolyon
May 22nd, 2007 at 5:07 am
This wouldn’t be unprecedented, either, Breeze (Connect) requires an additional small download the first time.
May 22nd, 2007 at 6:53 am
yoyo,
Right, although I believe you’re downloading a different version of the player in that case rather than installing a module to enhance your current one. But the concept from the user’s perspective is certainly the same.
May 22nd, 2007 at 11:24 pm
hi tom,
if you don’t move the mouse at all and never reload the page you won’t have these problems.
yeah, thats awful. here’s the sorta good news. a few years ago all the browsers had that effect. now the majority of browsers render these fine. fine = stable. (companies are using the html component in production). my strategy is/was to put this component out there, make you wish your browser could support it, have you and every other Flex developer email the browser development teams that don’t currently support it as fully as they should and get the few remaining issues fixed. looking back at HTML Overlay component i wrote 3 years ago, a lot has been fixed in this area.
i looked into the safari issue before. as we both know, the latest build has the fix. (haven’t tested it though. send them the example pages.) but this bug not only affects this component it affects every flash movie that has a div pop over it. for example, dropdown comboboxes that have a flash object beneath it. the combox or div menu produces the same flicker or they are hidden and they aren’t using the html component. this bug occurs even on adobe.com’s header menu. so the first issue is to get this fixed no matter what. that should cascade down to a lot of issues. my question is when will the next version of safari come out?
having said all that, the best thing you can do is send requests to the adobe wishlist. i’ve developed the html component because i have a feeling this is not on their list of priorities (people have been asking for an html control or better html support since I can remember, version 6 for me).
i would love to have the webkit browser control (aka Apollo HTML Control) in the Flash Player runtime. i don’t think it isnt out of scope for them to add something like this into the flash player. the external interface api is a perfect example of what adobe can do when people ask for it. …ok, i’m rambling.
July 14th, 2007 at 12:07 pm
Have you tested this in the new Safari browser?