This should be the final version for a while. After the feedback from the last two releases I think I have fixed all the major bugs (at least the ones that are not part of the Flash Player or Browser).
Fixes:
* HTML Component elements are hidden properly to work around a bug in Firefox. Click on GetHTML and then try and close the pop up. Try right clicking. See the bug in this example here. This has been fixed, as in workaround, in this release.
* ASDocs have actual documentation. In the last version the parser didnt pick up the doc comments.
* Updated Quickstart Guide. Installation instructions revamped and now with images.
* Works much better with pop ups.
* Updated examples.
* Fixed a few minor bugs
Live Examples
* HTML Component using an IFrame
* HTML Component using a Div
* HTML Component displaying a Rich Text Editor (upload disabled)
* HTML Components in a TabNavigator
* HTML Components in an unsupported browser
* HTML Component displaying PDF
Please note. Version 2 is free (scroll down).
UPDATE (March 9, 2008): Hi guys, since Flex 3 was released I’m taking version 2 down. It has been free for a year (just cause I like you guys), version 2 doesn’t work with Flex 3 and has a few bugs with pop ups. Version 3 fixes these issues and is available for purchase to cover ongoing development and support costs so I can pay my rent. If you want to keep me from living under a bridge purchase version 3 with or without the source code here. BTW I am upgrading the support channels for this component so assistance should be even faster. PS I have a lot of cool stuff I want to get out. Hoping to show you guys soon!
After viewing any of your examples as well as trying out the code for myself, the initializing of the component seems to always produce this error.
TypeError: Error #2007: Parameter type must be non-null.
I don’t ever seem to find anything wrong with the component, and due to it being a swc I can’t really troubleshoot the source to give a better description but just thought I’d let you know.
I wrote a similar component for our application, and just found a bug in it due to WMODE opaque in IE. Looking around to see if anyone has a solution, I found that your component has the same problem.
In IE (6 or 7) if your Iframe gets input focus, it does not give it back to flash. Try your Iframe sample, browse to google and start typing in the search field, then try typing anything into your Flex app – you’ll find all keypresses still go into the google search field.
I’m guessing I’ll have to get Flex to detect a FOCUS_IN, and use ExternalInterface to tell the Iframe to lose focus. I’ll post back if I find a nice solution.
@Travis – I’ve never seen that bug. Does it show up on the examples on the site? What FP and FB are you using? You must use 2.0.1 Hotfix 2.
@Grant – Please do. I have confirmed this bug. Please goto http://bugs.adobe.com/flex and report this bug. This is something the Flash Player or Flex team would have to fix. Update: A workaround for this issue is in the bugbase, check http://www.drumbeatinsight.com/forums – faq for links to the code.
We had trouble with the new wmode value in the index.template.html — set to opaque. While the HTML Component showed up in pop-up, etc., (where it previously did not), some of our state changes were adversely affected by the opaque setting.
Suggest setting wmode to transparent, for folks encountering this problem.
Hi Brad,
Can you explain adversely affected? The only issue I have run into is when I do not have *any* wmode set, the html component is blank or flickers but as soon as I add wmode opaque it works.
STATE ISSUES
The app has a small banner of text running vertically on the left side. As the states change, so does the text (label) attributes. When wmode was set to opaque, the y attribute change was momentarily delayed, causing the text value to change without the label repositioning itself — with the text either positioned too high and hanging over into another portion of the page or the text too low and not adjacent to the top of that particular section.
It was only delayed for about a second — and then the text would shift back to the new, correct y value. I’m at a loss as to this behavior. The state issue didn’t occur when no wmode was set (which really defaults to window), but obviously the html component was blank (IE) and flickered (Firefox). In this instance, both the state changes and the html component work when wmode is set to transparent.
IFRAME POSITIONING
On an unrelated note, I have a question regarding centering the application and it’s effect on the position of the iframe… I attempted to put your component into a TitleWindow pop-up box, which I auto centered after creating using PopUpManager.centerPopUp(). Works great when no width and height attributes are included in the application tag, but does not when centering a smaller app on a larger html page. The position of the iframe is off by the amount of the pure html (dead) space on the left of the centered flex SWF.
It appears that the html component uses the relative x and y flex values when inserting the iframe into the dom and not absolute x and y values. One suggestion might be to account for the difference by using externalInterface Javascript calls of availHeight and availWidth. Then a moveTo call or just absolute positioning when inserting the iframe into the dom — although I’ve not really thought this through fully, though.
Impressive component! Great work, Judah. Thanks
Does this work in Flex3 Beta? I can not seem to get it work thou.
nD – It works in Flex 3 beta using the SDK 2.0.1 Hotfix 2. If that is what you are compiling with what issues are you having? I have not tested it yet with the moxie sdk. The framework is still changing and I don’t want to have to determine if a bug is caused by my component or the framework. But its on the list for Flex 3 SDK3 compatibility.
Hi
Does anyone have a workaround for the focus problem described by Grant? It seems to be the same when setting wmode to transparent. By setting it to window the iframe will loose focus but will also disappear.
Just wanted to add an interesting observation i made trying to figure out this focus problem in IE. I’m using the fckeditor and when i fist collapse the toolbar then expand it again the focus is back on the flash??? I’m now trying to figure out what happens in js and try to use ExternalInterface from Flex to make it loose focus
Hello,
I have a problem using HTMLComponent on firefox : when setting wmode to opaque, all my textfields (textinput, textarea and so on) refuse special charaters such as @, ?, … or the numbers on the top of the keyboard (those on the right have no problem). It sounds that it is the key combination that is not token in count. If i remove wmode i can’t use HTMLComonent so is there a workaround ? I precise i am french (that’s why my english is so bad) and, so, i use azerty keyboard.
Thanks alot.
Hi!
I have the same problem like Milak. When I use wmode=opaque or transparent – all input fields doesn’t allow to use my national characters. Flex automagicaly replace this characters to another, ex:
? – a
ó – o
? – l
etc…
I have tried to set other parameters like lang and devicefont but without any success. :(
I’ve logged a list of bugs on Adobe’s bug system. Here is the list. If they get enough votes they will be fixed.
http://drumbeatinsight.com/forums/viewtopic.php?p=1001#1001
I briefly describe a workaround for the ie7 focus problem here: https://bugs.adobe.com/jira/browse/SDK-12377
Hi,
Is it possible to show a Flex Alert.show() popup over the HTML Component ?
Thanks
@Guillaume – In the browser you have the Flash swf and then on top of that you have an iframe or a div. They are separate elements stacked in order in the browser. What you can do is when you pop up an alert “hide” the html element using the htmlVisibility or the visible property. When the user closes the alert box then restore the visibility.
more info here…
http://drumbeatinsight.com/forums/viewtopic.php?t=662
judah, where is the free version 2 download?
Hi Kenneth –
Note: This version only works in Flex 2 and doesn’t support pop ups. It also has a few cases where visibility is not handled correctly but should work fine in the tested cases (IE the example cases).UPDATE (March 9, 2008): Hi guys, since Flex 3 was released I’m taking version 2 down. It has been free for a year, version 2 doesn’t work with Flex 3 and has a few bugs with pop ups. Version 3 fixes these issues and is available for purchase
to cover ongoing development and support costsso I can pay my rent. If you want to keep me from living under a bridge purchase version 3 with or without the source code here. PS I have a lot of cool stuff I want to get out. Hoping to show you guys soon!I’m using an Axis 241 video server which outputs imagery in RTSP. Works fine with QuickTime. I’m trying to add the ability to view live imagery in Google Earth (GE) when the user clicks a placemark. GE only allows the usage of a Flex/Flash app in their KML description tag. Many have requested they allow the usage of QuickTime there as well but nothing to date. I have a Darwin server running on my PC to supply RSTP video stream. If I place the following in a html document and serve it using Apache on my PC, QuickTime loads, and nicely shows the stream. So I was wondering, if I took your HTML component and put the following in it would it work?
I pasted this in your example at http://drumbeatinsight.com/examples/htmlcomponent/div/HTMLInApplication.html
and the QuickTime logo appears but nothing further. This just may allow me to pacify GE with a flash app but have it load QuickTime. That would be very cool!
Any suggestions?
wmode issue – We have also found that “Ctrl-Clicks” stop working in Firefox which also affects multiple selections in a DataGrid Component.
Hi,
I would like to show an iframe in full screen mode. Is this at all possible with your component? I don’t see it in the examples.
bye,
Ariel