Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <2823752.UaOU2mbOze@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Fri, 29 Mar 2013 23:27:54 +0100 User-Agent: KNode/4.8.5 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <632ccce8-2003-4597-b808-a77bee8b2852@googlegroups.com> <6235488.vrjhk3lj0x@PointedEars.de> Followup-To: comp.infosystems.www.authoring.html MIME-Version: 1.0 Lines: 62 NNTP-Posting-Date: 29 Mar 2013 23:27:56 CET NNTP-Posting-Host: 8ddaddab.newsspool3.arcor-online.net X-Trace: DXC=lU[L3]Nh_f;n`gW2MTm]<3McF=Q^Z^V384Fo<]lROoR18kF Danny wrote: >> see if this helps >> http://www.wufoo.com/html5/attributes/02-autofocus.html > > This is not the Web, you should not post only URLs as > suggestions/solutions. The approach suggested there is > > > > It is a good point, though. The relevant specification is: [HTML5 CR] It turns out that (at least in Chromium 25.0.1364.160 Debian 7.0 (186726)) the “autofocus” attribute causes the same usability issues as the focus() method when called in a “load” event listener: The document cannot be scrolled using the arrow keys. [Also, the control thus focused may still not be visible. This would need to be worked around with the scrollIntoView() method, which may not be available or functional, in a “load” event listener.] So this attribute is best avoided as well. Instead, the following approach is recommended: The “accesskey” attribute, which allows to use a keyboard shortcut so that the control receives the input focus, was introduced with HTML 4 [1] and is also supported in HTML5 (CR) [2]. The actual shortcut that focuses the control varies among browsers. In Chromium 25.0.1364.160 Debian 7.0 (186726) with a QWERTZ keyboard layout, it is + + . The “placeholder” attribute and [the “type” attribute value further show the affordance [3] of the control. They can be augmented with a suitable “cursor” CSS property value.] Should the “placeholder” attribute not be supported (HTML 4), the “title” attribute (HTML 4+) can provide the description, perhaps (but not necessarily) as a tooltip [4, 5]. [It is also common and recommended to put a short, unobtrusive (e.g, darkgray) descriptive text above, next to, or below the control [6]; but whether this is suitable for you depends on the viewport dimensions and other factors.] [1] [2] [3] [4] [5] [6] -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.