[whatwg] Context help in Web Forms

Ian Hickson ian at hixie.ch
Mon May 26 23:47:18 PDT 2008

On Mon, 12 Nov 2007, Matthew Paul Thomas wrote:
> On Oct 30, 2007, at 6:01 PM, Ian Hickson wrote:
> > On Mon, 13 Jun 2005, Matthew Thomas wrote:
> > > 
> > > Or perhaps <a ... rel="help" for="phone-number">, to be consistent 
> > > with the for= attribute in <label>.
> > 
> > This is a possibility, but is it really needed? In general it seems 
> > we'd want to encourage authors to put the links near the text and 
> > controls to which it applies.
> Sure, but I don't see how it's different from <label> in that respect: 
> we want to encourage authors to put <label> near the control to which it 
> applies, but <label> already has for=. (<label> can have weak semantic 
> value even when not related to a particular control, but then so could 
> rel="help".)

I'm not sure I would have designed <label> as it is either.

> > > Many applications provide inline help which is not a label, and the 
> > > same attributes would be appropriate here: <div rel="help" 
> > > for="phone-number"><p>The full number, including country code.</p> 
> > > <p>Example: <samp>+61 3 1234 5678</samp></p></div>
> > 
> > How would UAs use this?
> UAs likely wouldn't, but scripts could. For example, a form might 
> include sparing help by default, with a style sheet hiding more 
> exhaustive help (as indicated by rel="help"). Then a script could add a 
> small help button after each control that has associated help (i.e. each 
> control with name="x" where there exists an element on the page with 
> rel="help" for="x"). When a control's help button was clicked, the 
> control's help would be shown.
> Another possible presentation would be reserving whitespace to the right 
> of the form, and making <whatever rel="help" for="x"> visible in that 
> space whenever <input name="x"> was focused.
> <http://uxmatters.com/MT/archives/000191.php> shows these and other 
> examples of dynamic help.

The data-* attributes are intended for scripts like this.

> > > The majority of authors still wouldn't use these attributes, because 
> > > it would give them no presentational benefit. But at least authors 
> > > would be slightly more likely to use them than to use attributes 
> > > that they have to re-present using extra elements or JavaScript.
> > 
> > We should probably aim higher than that though... ...
> I'm suggesting either replacing <foo cite="url"></foo> with <bar 
> rel="citation" for="id-of-foo">, or dropping cite= altogether.

<blockquote cite>, <q cite>, <ins cite>, and <del cite> are still in HTML5 
for now. I don't see the point of adding a new attribute for this, given 
how so few people care anyway.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list