jQuery Forum

Hi folks,
We have had a couple support requests we have been unable to reproduce
locally, and I was wondering if anybody else has run into similar
problems. Two separate Mac Safari users have complained that when
they get to a certain question on our form, which happens to be the
first one that has a datepicker associated with it, the browser
crashes. The first user has this user agent string:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_5_2; en-us) AppleWebKit/
525.13 (KHTML, like Gecko) Version/3.1 Safari/525.13
... and reported, "I have attempted it 3 times now. Each time I get to
the part where I am to enter dates it causes Safari to quit and
everything is lost."
The second user with this user agent string:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_2; en-us) AppleWebKit/
525.13 (KHTML, like Gecko) Version/3.1 Safari/525.13
... said: "I got to question 28 [the datepicker one] three times and
the system shut down."
Unfortunately, when we install Safari 3.2.1 on our test Mac, the
datepicker on that page works fine, so we can't really debug it.
We are running UI 1.7.1. I see there is a 1.7.2 upgrade, but I don't
see anything in the changelog that suggests this is a known problem,
or that it might have been addressed in that release.
Any ideas?
Thanks!
Jim

Hi folks,
I'm running UI 1.7.1, and just noticed that the links in my tab
content are not using my site styles, and are instead using the tabs
styles. I gave it a quick look in Firebug, and indeed the style for
".ui-widget-content a" is trumping my style for "a, a:visited". I
thought I must have missed a setting in Themeroller when I generated
the style, but when I reloaded my style I couldn't find a setting
anywhere that maps to ".ui-widget-content a". I can change the
"content" text color, but that changes all text inside the tab
(widget), not the links. I could edit the Themeroller-generated CSS
directly, but I don't want to do that because then I've lost one of
the very cool Themeroller features: namely, the fact that it
generates a URL from which I can reproduce and tweak my theme, and
presumably upgrade the theme as UI upgrades and evolves.
Is there a way for me to address this short of manually editing the
Themeroller-generated CSS? Or am I missing some other way?
Thanks!
Jim

Hi folks,
Another small issue with my recent upgrade to UI 1.7.1. I have some
Ajax tabs that, once they load, contain tables of varying size. The
tab container does not seem to expand to accommodate the height of the
table, so the border around the tab dives behind the table.
Screenshot here, arrows pointing out the issue:
http://www.biancolo.com/jim/tabs_border.jpg
I'm currently working around this with this code:
$('#tabs').bind('tabsshow', function(event, ui) {
var list = $('.recipient_list', $(ui.panel));
var tab = list.parent();
tab.height(tab.height() + list.height());
});
It's a bit kludgy, as it tends to expand the tab container more than
necessary, but it's better than it being too small.
Is there a fix or a better way or something I'm doing wrong?
Thanks!
Jim

Hi folks,
I'm using UI 1.7.1 and I tried to make use of the new cookie "name"
option, but when I do the act of clicking on a tab makes the page
scroll down like it's going to a named anchor. When I back this
change out and go back to my old tab/cookie code the behavior returns
to normal (no scroll on switching tabs). This behavior is bizarre
enough that I assume the problem is with my code, but so far I haven't
been able to run it down, so thought I'd mention it in case anybody
else has run into the same thing.
Thanks!
Jim
P.S. In theory I'm psyched about the "name" option, as I have
different pages that make use of tabs that share the same controller
name, so I needed a way to distinguish the cookie name so the right
tabs would load on such pages. For now I guess I'll keep using my old
code, which was to code the cookie/tab logic by hand via $.cookie.

Hi folks,
I'm using the cookie plugin to make the selected tab sticky, using
this syntax:
$('#tabs > ul').tabs({cookie: {expires: 7}})
I have several pages that use this syntax, and some of the pages
appear to "share" a cookie, in that the selected tab on one page then
also becomes the selected tab on another page. Is there a way to
specify a different cookie name for each page so there's no conflict?
I tried this, but it had no effect:
$('#tabs > ul').tabs({cookie: {name: 'foo', expires: 7}})
Thanks!
Jim