I found a couple of minor jQuery issues. Fixed here: JSFiddle. This line: $(‘*’).attr(‘tabindex’, tabindex).focus(); can be written like this: $(‘[tabindex=’ + tabindex + ‘]’).focus(); and this: $(‘#Msg’).text($(this).id + ” tabindex: ” + tabindex + ” next element: ” + $(‘*’).attr(‘tabindex’).id); is not calling the id attribute the jQuery way (you are using JavaScript syntax, … Read more
Between leaving the old element and entering the new element the active element is indeed the document/body itself. Demo: http://jsfiddle.net/u3uNP/
Ok, somebody explained this to me. It’s a Mac problem. Mozilla is being true to operating system settings in Mac OS. There are two distinct ways around this on the user side. Both seem to work: In System Preferences → Keyboard, in the Shortcuts pane, check the “all controls” radio at the bottom. In Firefox, … Read more
DIV elements are not compatible with tabindex in HTML4). (NOTE HTML 5 spec does allow this, however, and it commonly works regardless) The following elements support the tabindex attribute: A, AREA, BUTTON, INPUT, OBJECT, SELECT, and TEXTAREA. Essentially anything you would expect to be able to hold focus; form elements, links, etc. What I think … Read more
tabindex is a global attribute responsible for two things: it sets the order of “focusable” elements and it makes elements “focusable”. In my mind the second thing is even more important than the first one. There are very few elements that are focusable by default (e.g. <a> and form controls). Developers very often add some … Read more
You can use tabindex=”-1″. The W3C HTML5 specification supports negative tabindex values: If the value is a negative integer The user agent must set the element’s tabindex focus flag, but should not allow the element to be reached using sequential focus navigation. Watch out though that this is a HTML5 feature and might not work … Read more