Opened 13 years ago

Closed 13 years ago

Last modified 10 years ago

#5315 closed bug (duplicate)

tabs add() method moves panel element even when it already exists

Reported by: JAAulde Owned by:
Priority: minor Milestone:
Component: ui.tabs Version: 1.7.2
Keywords: tab tabs add DOM Cc:
Blocked by: Blocking:


If I add an element to the DOM in a container which has already been tabbed, and call add() [tabs('add')] with the new element's ID as the href, UI moves the new element from its location in the DOM to become a direct child of the tabbed container. (I am adding the element as a "grandchild" of the tabbed container)

Though I am using an unsupported DOM structure, tabs() works correctly on the same structure (panels as grandchildren) when initially building tabs. But an added panel in the same fashion BEFORE I call add() results in the element being moved from where I had added it.

I discussed this on the forums with Richard Worth: where I also provided test cases. A read of that forum thread followed by a view of the linked test cases should provide all necessary background information.

Richard stated, and I agreed, that UI will not provide support for my DOM structure. However he said the move of my previously added panel by the add() method could very well be a bug and welcomed me to create a ticket. This is especially the case since the initial buildout uses add() internally and does not suffer the same problem.

Thanks, Jim

Change History (2)

comment:1 Changed 13 years ago by Scott González

Resolution: duplicate
Status: newclosed

Duplicate of #4578.

comment:2 Changed 10 years ago by Scott González

Milestone: TBD

Milestone TBD deleted

Note: See TracTickets for help on using tickets.