vertical_tabs_add_vertical_tabs() does not work with Safari/Webkit 4.x
ptoly - September 16, 2009 - 14:24
| Project: | Vertical Tabs |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
I've put in this small snippit in my custom module:
// Add vertical tabs to profile form
if($form_id == 'user_profile_form')
{
vertical_tabs_add_vertical_tabs($form);
}
This works great on FF Mac/PC and IE 7/8 but dies completely in Safari - nothing is rendered at all in the form.
Safari/Webkit vertical tabs work fine for the default module setup. It just seems to fail on this custom function call.
I need to do some more research on this and I'd like to know if anyone else has seen this issue?
Thanks!
#1
I have similar problem. Vertical Tabs was working (Google Chrome) until I upgraded to Drupal 6.14 yesterday. Right now it just look like I have never installed Vertical Tabs in Google Chrome but VT is still working in Firefox.
Google Chrome upgraded itself last night and I upgraded to Drupal 6.14 at around the same time so I am not sure which is causing the problem...
#2
I am using the module with Drupal 6.14, and I don't have problems with Safari, which shows me the user interface as I would expect (see the attachment).
#3
Actually I have just noticed that VT works fine even in Chrome ONLY when you're logging in as a non-admin user
#4
I believe the problem is jQuery. We just started having this problem with vertical tabs in Safari, everything started breaking. I just realized it started when we installed the jQuery Update module (another module requires it).
When I turn off jQuery Update, vertical tabs starts working again.
#5
An update on my comment #4 ...
The problem I just described (jQuery Update + VT incompatibility) does indeed happen on Safari 3.2.1. VT does appear to break entirely with newer version of jQuery on that Safari version.
But, happily, on Safari 4.0.3, VT appears to work perfectly even with the newer versions of jQuery.
Which is good, because I forgot just how miserable it feels trying to debug js problems without Firebug!
Of course, this may have nothing to do with the other comments posted here, but passing along some info.
#6
garywiz, thanks!
#7
Automatically closed -- issue fixed for 2 weeks with no activity.