Such usage does not seem to be semantic, as we are really not going to make focusable part a hyperlink
if the child content could not be redefined by end developer - I think it's most simple and elegant solution. So we have to decide how much we want to sacrifice in order to be "semantic"
Nested A elements are not allowed, so user won't be able to place hyperlink for example in tab label area
This however is more serious problem and could be the reason to reject this idea. But how about to use <a> explicitly encoded as anchor and not to wrap the content itself? something like :
<div> <a>//some fake anchor which will handle the styling of the whole div when focused/leaved//</a> actual label content </div>
not looks really good but just rough idea.
Browsers have built-in styling for A element, that we'll have to override
I believe that not a big deal which could be solved by some common class for all such links.
About the second idea, especially about
and can decrease performance of page load.
This however should be estimated using some prototype in order to have clean vision for making decisions.
After discussions in IRC....
No one seems crazy about the <a> tag, and almost nothing in richfaces ( or any rich component set ) will work with JS off.
The idea of a tab index component/behavior seems worth looking into more.
We could handle cross-browser and technology issues in the tag, and give developers a single place to assign this.
After an IRC discussions we have decided to postpone this until one of the milestone releases.
I have created https://jira.jboss.org/jira/browse/RFPL-587 to cover this and have attached the IRC log to it.