With the current trunk (1.99.7?) you can set content='' have have the message invisible. or content=None and in that case you have to make your own target div.
On Saturday, 3 March 2012 12:01:25 UTC-6, Alan Etkin wrote: > > OK. So now, if I want to avoid the default "...loading" message in an > extra tag I can call LOAD() with content=None > > I'll try something else so when calling the function the content=None > is guessed. > > On Mar 3, 2:32 pm, Massimo Di Pierro <[email protected]> > wrote: > > Not your fault. I should have checked. The problem is that when > > LOAD(....target=None) after the patch the <div > id="{{=target}}">..</div> > > is no longer displayed. > > > > > > > > > > > > > > > > On Saturday, 3 March 2012 11:14:39 UTC-6, Alan Etkin wrote: > > > > > Why did my patch break backwards compatibility? I think that the > > > problem I mentioned in other thread about the remaining "...loading" > > > will appear again if is LOAD called with a no default target argument. > > > > > On Mar 3, 3:02 am, Massimo Di Pierro <[email protected]> > > > wrote: > > > > Bruno has reported a backward compatibility issue with LOAD with > 1.99.6. > > > > The issue is fixed in trunk but I will wait tomorrow to post 1.99.7 > just > > > in > > > > case something else arises. > > > > This was the biggest release in meny months so we need to iron some > > > corners. > > > > > > Sorry for the inconvenience. > > > > > > Massimo
