Path: csiph.com!usenet.pasdenom.info!gegeweb.42!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <4191797.g0LvDaAvTT@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sat, 10 Mar 2012 01:42:25 +0100 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 7Bit Subject: Re: Removing a Control from the taborder Newsgroups: comp.lang.javascript References: <1fuil7tf54q4gu2h40ous7k58q3766aaa9@4ax.com> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 44 NNTP-Posting-Date: 10 Mar 2012 01:42:25 CET NNTP-Posting-Host: bbe473ab.newsspool3.arcor-online.net X-Trace: DXC=7_aR6O?JfSOC4i^e1BZ=_HMcF=Q^Z^V3H4Fo<]lROoRA8kF1UjV_2lD X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:12562 Norman Peelman wrote: > Consider this, the tabindex controls the tab order of the form > elements with a range of 0 - 32767. That means to remove a form element > from the tabindex it must not be in that range. "-1" is not in that > range, nor is "-32767" or anything in between for that matter. You could > simply throw (insert) a minus sign in front of a form element to disable > it, even via scripting (simply multiply the tabindex by -1 to toggle). Your logic is flawed. The HTML 4.01 Specification is definitive about this: values for the `tabindex' attribute outside the specified range are *invalid*. It is specified accordingly in W3C DOM Level 2 HTML: However: > http://fluidproject.org/blog/2008/01/09/getting-setting-and-removing- tabindex-values-with-javascript/ It is disturbing to see that HTML5 would allow authors to create focusable elements that could not be reached with basic keyboard navigation, making those documents not accessible: There is also an inconsistency here: HTML5 must not allow values for attributes already specified in HTML 4 that cannot be set using a conforming implementation of W3C DOM Level 2 HTML. Either HTML5 renounces its backwards compatibility with HTML 4, or it must specify the attribute value differently. Bottom line: There is no public standard to back up your approach as of yet. It is likely to be not interoperable, and it is certain to be not accessible if supported. The range of your research is far too narrow to make a case for the adoption of this approach. PointedEars -- Danny Goodman's books are out of date and teach practices that are positively harmful for cross-browser scripting. -- Richard Cornford, cljs, (2004)