> I just figured out that the deal is that SWFObject doesn't > like to be set visible false on page load then visible true via Ajax. > > Any thoughts on how to get around this?
Ajax in Wicket needs the page DOM to have an element with the id it is supposed to replace with the output of a (now visible) component; by default an invisible Wicket component has no output at all. The traditional way to overcome this is to call setOutputMarkupPlaceholderTag(true) on the (initially invisible) component when you add it; that will make Wicket insert an empty element with the required id. (It also implicitly calls setOutputMarkupId(true) which is something else that the Ajax support needs to work properly.) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
