Ian Hickson wrote:
Actually, the way the spec is written now, the UA _can_ assume that the
title attribute is going to help. In fact it is encouraged.
Assume that your proposal (hint) is spelt title and implement it like
that. (Including the little button you wanted for hint). That is the
On Fri, 7 Oct 2005, Matthew Raymond wrote:
There is a certain presumption that the author doesn't want to use
|title| for any other purpose than providing input hints. This is
potentially erroneous. For instance, the |title| may describe the
purpose of the input rather than the input
Ian Hickson wrote:
On Thu, 4 Aug 2005, Dean Edwards wrote:
Actually, the way the spec is written now, the UA _can_ assume that the
title attribute is going to help. In fact it is encouraged.
Assume that your proposal (hint) is spelt title and implement it like
that. (Including the little
On Mon, 29 Aug 2005, Dean Edwards wrote:
Ian Hickson wrote:
On Thu, 4 Aug 2005, Dean Edwards wrote:
Actually, the way the spec is written now, the UA _can_ assume that the
title attribute is going to help. In fact it is encouraged.
Assume that your proposal (hint) is spelt title and
On Wed, 3 Aug 2005, Dean Edwards wrote:
I know this has been suggested before, and was rejected, but I would
quite like to see a pattern hint attribute added to Web Forms 2.0.
With more complex input controls we should spare a thought for the poor
user.
There is one. It's the title
On Thu, 4 Aug 2005, Dean Edwards wrote:
I'm also concerned about pattern mismatches. If a form is invalid the UA
is supposed to feed back information to help the user complete the form.
http://whatwg.org/specs/web-forms/current-work/#form-submission
For most types, pattern mismatches
Dean Edwards wrote:
I know this has been suggested before, and was rejected, but I would quite
like to see a pattern hint attribute added to Web Forms 2.0. With more
complex input controls we should spare a thought for the poor user.
fantasai wrote:
Dean Edwards wrote:
I know this has been suggested before, and was rejected, but I would
quite
like to see a pattern hint attribute added to Web Forms 2.0. With more
complex input controls we should spare a thought for the poor user.
Dean Edwards wrote:
fantasai wrote:
Dean Edwards wrote:
http://www.whatwg.org/specs/web-forms/current-work/#the-pattern
That is not enough. I wouldn't put something so complex in a tooltip. It
would frighten my users.
What could be so complex that would frighten users when used in a title
Lachlan Hunt wrote:
Dean Edwards wrote:
fantasai wrote:
Dean Edwards wrote:
http://www.whatwg.org/specs/web-forms/current-work/#the-pattern
That is not enough. I wouldn't put something so complex in a tooltip. It
would frighten my users.
What could be so complex that would frighten users
Dean Edwards wrote:
Matthew Raymond wrote:
Lachlan Hunt wrote:
Dean Edwards wrote:
fantasai wrote:
Dean Edwards wrote:
http://www.whatwg.org/specs/web-forms/current-work/#the-pattern
That is not enough. I wouldn't put something so complex in a
tooltip. It would frighten my users.
I know this has been suggested before, and was rejected, but I would
quite like to see a pattern hint attribute added to Web Forms 2.0.
With more complex input controls we should spare a thought for the poor
user.
I've been trying to think of ways to feedback pattern mismatch help info
but
12 matches
Mail list logo
