A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).

Change Proposal for ISSUE-144

From WHATWG Wiki
Revision as of 04:42, 23 March 2011 by Hixie (talk | contribs) (Created page with 'This is the CCP against [http://www.w3.org/html/wg/wiki/ChangeProposals/UShouldBeConforming ChangeProposals - U Should Be Conforming]. == Summary == There is no new use cases a...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This is the CCP against ChangeProposals - U Should Be Conforming.

Summary

There is no new use cases addressed by the <u> element.

Rationale

  • All the reasons a human author might have to use <u> already have more appropriate elements, except the two cases given in the CP. They are both too rare on the Web to be considered valid use cases.
  • If we were to address the use case of content generated by an authoring agent, the same argument should be applied to <font>, <big>, <layer>, <blink>, <tt>, <center>, align="", etc.
  • An underlined text which is not a hyperlink confuses the user in his/her browsing experience.

Details

No change.

Impact

Positive Impact

Authors will have to use appropriate semantic markup for applying underlines. (e.g. <ins> for insertion, <em> for emphasis, etc.)

Negative Impact

None.