I discovered that the problem isn't tacos, it's tapestry. When i rolled back to tapestry 4.0 from tapestry 4.0.2, it worked again. My tapestry 4.0 jar might have been patched for the bug I mentioned in the first mail...
On 9/14/06, Inge Solvoll <[EMAIL PROTECTED]> wrote:
Also tried making it client only by removing the listener, same error. On 9/14/06, Inge Solvoll <[EMAIL PROTECTED] > wrote: > > Hi, thanks for answering! > > This is a regular web app, not a portlet. I've never used portlets. > > I'm pretty sure this is the only tacos component I'm using. I'll see if > I can mount up another one to check. > > Of course the javascript I'm running could be cached. But I don't think > so, IE has been restarted and normally the things I've done should be > sufficient to clear the cache of my IE. > > I discovered that the section that initializes and imports dojo had been > duplicated, I removed the duplicate, made no difference. > > Has there been made some kind of localization changes to tacos recently, > that may have caused some bad characters in the js-code, like in the bug > referenced? > > Here's the relevant excerpts html code generated (works in Firefox > 1.5.0.6): > > HEAD section: > > <script type="text/javascript" > > > djConfig = { isDebug: false, > baseRelativePath: "/moby/script/dojo/", > preventBackButtonFix: false }; > </script > > > > <script language=JavaScript src= > "/moby/script/dojo/dojo.js" type="text/javascript"></script> > > > > <style> > div.auto_complete { > > width: 500px; > background: #fff; > } > div.auto_complete ul { > border:1px solid #888; > > margin:0; > padding:0; > width:100%; > > list-style-type:none; > } > div.auto_complete ul li { > margin:0; > padding:3px; > > } > div.auto_complete ul li.selected { > background-color: #ffb; > > } > div.auto_complete ul strong.highlight { > color: #800; > margin:0; > > padding:0; > } > </style> > > > BODY: > > <input type= > "text" autocomplete="off" value="" > name="autoCompleter" id="autoCompleter" class= > "auto_complete" onclick="this.select()"/> > > > AFTER END TAG OF FORM: > > <script language="JavaScript" type= > "text/javascript"><!-- > Tapestry.register_form('Form'); > > > > tacos.createAjaxAutocompleter("autoCompletercomplete", "autoCompleter", " > > http://localhost/moby/ajaxdirect.svc?component=autoCompleter&page=SettingsEdit&rand=-1184249844&session=T&sp=SautoCompleter&updatedirect=true&updateid=autoCompleter", "auto_complete", > > 0.2, > {}, {}); > > > // --></script> > > > > On 9/13/06, andyhot < [EMAIL PROTECTED]> wrote: > > > > Does this happen in portlets? > > Do other tacos components work ( i.e. AjaxDirectLink) ? > > Are you sure the browser doesn't load the old javascript (due to > > cache) ? > > > > If nothing works, is it possible to show us the rendered html ? > > > > > > Inge Solvoll wrote: > > > After upgrading to tapestry 4.0.2 and tacos 4.0.0, my page with > > > autocompleter does not work anymore. I get the behaviour described > > in the > > > tacos FAQ about IE problems: > > > > > > http://tacos.sourceforge.net/faq.html#faq-N100A2 > > > > > > The page loads in IE when the autocompleter is removed, when the > > > autocompleter is there, IE cancels page load and displays the error > > > dialog > > > described in the link. > > > > > > The solution suggested doesn't apply to me, because I don't use the > > shell > > > component, and no base tag is rendered. > > > > > > Any ideas? I've been through similar symptoms before, with the > > > datepicker in > > > contrib, bug report here: > > > http://issues.apache.org/jira/browse/TAPESTRY-788 > > > > > > > > > -- > > Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr > > Tapestry / Tacos developer > > Open Source / J2EE Consulting > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >