Skip to main content

Search and Top Navigation

#7676 closed bug (notabug)

Opened August 29, 2011 12:33PM UTC

Closed August 29, 2011 05:04PM UTC

Last modified December 07, 2012 08:14PM UTC

data driven tabs and routing mix up

Reported by: robbaralla@hotmail.it Owned by:
Priority: minor Milestone: 1.9.0
Component: ui.tabs Version: 1.8.12
Keywords: Cc:
Blocked by: Blocking:
Description

Hello there,

I have the following scenario, I use asp.net 4.0 with routing.

To use the jQuery tabs, the <a> in the <li> of the <ul> gets it's href from a data source through code. Also the content divs get their ID from code, so that every <a> would select the according div.

And as long as I do not use a custom route this works fine.

However when I call this page from a custom route, it becomes a mess: inside the page there is another page, the <a> elements are no longer refering to the divs, it seems that other divs are created with an Id like Id= “ui-tabs-NUM”. The browser even goes in tilt after a bit.

The only work around I found, was hardcoding the UL, but this really was not my intention.

any suggestions?

Attachments (0)
Change History (4)

Changed August 29, 2011 05:04PM UTC by scottgonzalez comment:1

resolution: → invalid
status: newclosed

Please use the forums for help.

Changed December 07, 2012 05:57PM UTC by johntrepreneur comment:2

I'm also having this very same problem. JQuery tabs + Asp.net routing = not working on Safari with behavior as described above with same page nested within the div, etc...

I checked and asp.net routing works fine with bookmarks, just not with the JQuery tabs. I also checked and JQuery tabs works fine in asp.net withOUT the routing feature.

Would you mind to share a quick description of a workaround you know of or some type of fix? Seems that the page gets messed up with the introduction of the anchors with bookmarks. I've been playing with the anchors trying different things, but no luck so far. Any ideas?

Changed December 07, 2012 08:04PM UTC by johntrepreneur comment:3

Found it. When using Asp.Net routing with JQuery tabs the content gets messed up in Safari when using %2C in the URL. %2C is the encode for a comma, but replacing it with a regular comma in the URL fixes the problem (if you can do that to your url). Once all %2C text is removed from the URL, asp.net routing works fine with JQuery tabs.

Changed December 07, 2012 08:14PM UTC by scottgonzalez comment:4

_comment0: IF this is limited to Safari 5.1, then it sounds like you're running into #8877.1354911287021420

If this is limited to Safari 5.1, then it sounds like you're running into #8877.