Wicket already looks if the css is already added or not before adding it. But in a single page full ajax component replacement where the components are panels that bring there own css then eventually we have a problem if you use more the 30 panels (is pages) that add there own css.
On 1/30/08, Michael Chang <[EMAIL PROTECTED]> wrote: > On Jan 29, 2008 8:52 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > > http://support.microsoft.com/default.aspx/kb/262161 > > > > In a full ajax page where you constantly are replacing panels and those > > panels have there own css > > then after 30+ panels with there css references IE will not apply the rest > > anymore! > > > > does anybody have seen/encountered this before and knows a workaround ? > > Is it necessary to reload the CSS every time you load a panel? Why > wouldn't you load one (or max 30, if you REALLY need that many) CSS > files with the AJAX code, rather than loading it with each panel? > > -- > Michael Chang > > Please note that not all formatting may be preserved in > Office/Word/Powerpoint documents sent to me. Please use OpenDocument > (not Open XML), HTML, and RTF where possible. See > http://www.gnu.org/philosophy/no-word-attachments.html > Thank you. >
