Skip to main content

Search and Top Navigation

#9920 closed bug (notabug)

Opened March 20, 2014 09:51PM UTC

Closed March 21, 2014 01:36AM UTC

Last modified March 21, 2014 12:23PM UTC

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?

Attachments (0)
Change History (6)

Changed March 21, 2014 01:36AM UTC by scottgonzalez comment:1

resolution: → notabug
status: newclosed

Sorry, that's just how HTML works.

Changed March 21, 2014 02:08AM UTC by pwrelkin comment:2

Replying to [comment:1 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?

Changed March 21, 2014 02:30AM UTC by scottgonzalez comment:3

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

Changed March 21, 2014 02:42AM UTC by pwrelkin comment:4

Replying to [comment:3 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?

Changed March 21, 2014 12:21PM UTC by tj.vantoll comment:5

Replying to [comment:4 pwrelkin]:

Replying to [comment:3 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.

Changed March 21, 2014 12:23PM UTC by scottgonzalez comment:6

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.