tabslider "stuck" when deployed SOLO

[johnafitch]

I have a tabslider that works fine when using local data, but when deployed SOLO is "stuck" on the first tab. Clicking the second or third tab clears the contents of tabelement #1, but the second and third tabelement never move up and display their contents.

My simplified code:
<tabslider name="mymenus" datapath="site_ds:/thissite/menu[1]"
defaultselection="0" x="10" y="125" width="160"
height="${parseInt(thisuser.screenw)-580}" >
<tabelement name="menu1mydec" datapath="menuitem1[1]" text="$path{'@mname'}" >
<-- TAB CONTENTS - A RADIOGROUP -->
</tabelement>
<tabelement name="menu1maked" datapath="menuitem1[2]" text="$path{'@mname'}" >
<-- TAB CONTENTS - ANOTHER RADIOGROUP -->
</tabelement>
<tabelement name="menu1mypref" datapath="menuitem1[3]" text="$path{'@mname'}" >
<-- TAB CONTENTS - A VIEW-->
</tabelement>
</tabslider>

When operating in local mode, I was populating tabelement text from a site.xml dataset. The tabslider height is set by a constraint that comes from a local user.xml dataset. When deploying SOLO, the user dataset is type="http" and its ondata handler then loads the site dataset.

Is there something about the order of construction for tabsliders that would make them behave differently between local data and http data with SOLO deployment? Or is there any other reason that makes a tabslider not slide?

This is quite urgent; I thought I was ready to deploy this really cool app before hitting this wall.

Thanks!
johnafitch