Setting the disabled state (attribute) on a tab does not act as I would expect.
The tab text will dull, and the onfocus event will not be executed. However, it
will still switch to the tab and display the tabpanel contents.
Dulling of text, non-execution of code and not allowing the tabpanel to be
Assigning to hewitt as per hyatt's request.
Created attachment 54861 [details] [diff] [review]
patch to disable opening of tab if disabled
question: how can one put a tab as disabled?
I only see close tab, close other tab, new tab, bookmark this group of tabs,
reload tab, reload all tabs.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927
Thomas: XUL is intended as a toolkit for building applications, and those
applications may have other uses for tabs besides just what Mozilla browsers
This patch looks pretty reasonable to me, but I'd need to further study other
bindings to ensure that this is implementing the disabled property in a
Reassigning to me so that this is at least on my radar.
The patch does nothing to address keyboard navigation between tabs.
> The patch does nothing to address keyboard navigation between tabs.
Neil, thanks for the info. Do you have time to revise the patch?
-> default owner
I'd say this patch has bit-rotted a bit. Anyone interested in me making another one?
*** Bug 360233 has been marked as a duplicate of this bug. ***
Can confirm this bug is still here FIVE YEARS after first report.
Tabs recieve focus whether they are disabled by property or attribute.
Maybe the next decade will bring a fix ;-)
Here are the other related bugs I found to the XUL tab.
Affected are the hidden, disabled attributes/properties as well as the ordering of tabs.
*** Bug 368069 has been marked as a duplicate of this bug. ***
requesting blocking1.9; this bug is ancient, relatively easy to fix (good first bug), and useful for Gecko app developers and extension developers.
Fixed by bug 370742