Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#9920 closed bug (notabug)

disabled tab anchors

Reported by: pwrelkin Owned by:
Priority: minor Milestone: none
Component: ui.tabs Version: 1.10.4
Keywords: Cc:
Blocked by: Blocking:

Description

Tabs that are disabled can still be accessed by adding the tab's anchor (ie: #tab) at the end of the URL. URL anchors should be disabled when tabs are disabled, since they provide access to tabs that are not ready to be viewed.

Also, could an option be added that prevents the selection of tabs through URL anchors all together? Even better, could the tabs be defined through an attribute other than href, to prevent the URL from being displayed in the browser when you mouse over a tab?

Change History (6)

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

Resolution: notabug
Status: newclosed

Sorry, that's just how HTML works.

comment:2 in reply to:  1 Changed 6 years ago by pwrelkin

Replying to scott.gonzalez:

Sorry, that's just how HTML works.

But why can't the tabs be linked to their panels in an attribute other than href? Why can't they behave like buttons rather than links? Wouldn't that remove the anchors and the mouseover text?

comment:3 Changed 6 years ago by Scott González

Your concern is about the panels having ids, not about the tabs having hrefs.

comment:4 in reply to:  3 ; Changed 6 years ago by pwrelkin

Replying to scott.gonzalez:

Your concern is about the panels having ids, not about the tabs having hrefs.

The panels could have ids that are defined in the tabs' class attribute or any other attribute. Why do they have to be defined in href, forcing the tabs to have anchors and act as links rather than buttons?

comment:5 in reply to:  4 Changed 6 years ago by tj.vantoll

Replying to pwrelkin:

Replying to scott.gonzalez:

Your concern is about the panels having ids, not about the tabs having hrefs.

The panels could have ids that are defined in the tabs' class attribute or any other attribute. Why do they have to be defined in href, forcing the tabs to have anchors and act as links rather than buttons?

It's about progressive enhancement / graceful degradation. The tabs widget starts with functioning links and falls back to functioning links.

comment:6 Changed 6 years ago by Scott González

And your complaint "Tabs that are disabled can still be accessed by adding the tab's anchor (ie: #tab) at the end of the URL" exists either way because of the id.

Note: See TracTickets for help on using tickets.