#6654 closed feature (wontfix)
Allow a tabs() option to specify the container which will hold panels
| Reported by: | dsh | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | ui.tabs | Version: | 1.8.6 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When allowing tabs() to auto-create panels, one has no control over where that panel will be created.
For our layout we need finer control on where auto-generated panels go.
Add an option "panelContainer" that specifies a selector or DOM element where auto-created panels will be placed.
[Patch coming shortly...]
Change History (3)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
This functionality is being deprecated in 1.9.
Note: See
TracTickets for help on using
tickets.
Couldn't you also just
.find('.ui-tabs-nav')and move it yourself? Although it might be nice to specify a selector other than ("ol,li").eq(0) for your tabs-nav...