Opened 15 years ago

Closed 15 years ago

#1253 closed enhancement (wontfix)

Enable/Disable specific tab in a tabcontainer

Reported by: Michael Schall Owned by: Adam Peller
Priority: high Milestone:
Component: Dijit Version: 0.3
Keywords: Cc: bill, dante
Blocked By: Blocking:


Tabs should be able to be dis/enabled through script.

Change History (5)

comment:1 Changed 15 years ago by dylan

Milestone: 0.5
Type: defectenhancement

comment:2 Changed 15 years ago by Adam Peller

Component: WidgetsDijit
Milestone: 0.9
Owner: changed from bill to koranteng

comment:3 Changed 15 years ago by Adam Peller

Cc: bill dante added
Owner: changed from koranteng to Adam Peller

Mike, disabled tabs isn't something I see a lot of. It might be confusing to the user, and I don't think we'd offer similar features, say in AccordionContainer?. We can add/remove tabs dynamically. Is that sufficient?

comment:4 Changed 15 years ago by guest

At our company we like a screen to look the same every time a user uses it. For example let's say you have a search screen that returns results for a contact. Tabs could be Addresses, Phone Numbers, Email Addresses, ... If no Phone Numbers exist for the current search, we would like to disable that tab. But if the user changes the criteria so that a phone number would be returned, we would enable the tab. Add/Removing? items from a screen confuses users. The same argument that applies for buttons applies here, if a button is not applicable at the time, it is disabled, not hidden/removed.

comment:5 Changed 15 years ago by Adam Peller

Resolution: wontfix
Status: newclosed

We talked it through, and this isn't going to be in dijit. However, you ought to be able to extend the current widget to do this with around advice around the tab's click event, and a little CSS styling to change the appearance of the tabs you mark. If there's something we can do to the base code to make this easier, let us know.

Note: See TracTickets for help on using tickets.