Not sure yet what the bug is actually, but I found that the following
fixes it:
setTimeout(function() {
tabdiv.children('#tabs').tabs("select","#tabs-2");
}, 0);
Lead me to changing the order of opening the dialog and selecting the
other tab:
content.dialog('open');
tabdiv.children('#tabs').tabs("select","#tabs-2");
which also works...
--Klaus
On 22 Feb., 02:48, mgl <mgl....@gmail.com> wrote:
> Hi all,
>
> I've found a bug in jQuery 1.3.2 (or maybe Dialog/Tabs in UI 1.6rc6).
>
> In my application, I have a dialog with tabs inside of it. I create
> the dialog and build/setup the elements inside it before it is
> displayed to the user. Up to jQuery 1.3.1 I haven't had a problem
> with this. Depending on what sequence of actions activates the
> dialog, a different tab will be selected by default, using the .tabs
> ('select',[tabid]) method. In some cases, this may happen before the
> dialog is displayed - this is where I've found a bug with jQuery
> 1.3.2. Basically, I get two tabs displayed. Here's an
> example:http://jsbin.com/umihi/edit
>
> If there are only two tabs, there's no way to fix it (in the example
> linked above, you can click on the 3rd, and it's okay after that).
>
> Is there any chance this has something to do with the latest changes
> to the Sizzle library?
