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 IRC (such as one of these permanent autoconfirmed members) or send an e-mail to admin@wiki.whatwg.org with your desired username and an explanation of the first edit you'd like to make. (Do not use this e-mail address for any other inquiries, as they will be ignored or politely declined.)

Note: This wiki is used to supplement, not replace, specification discussions. If you would like to request changes to existing specifications, please use IRC or a mailing list first.

Change Proposal for ISSUE-144

From WHATWG Wiki
Jump to: navigation, search

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, yet nobody is making such a case, suggesting that this rationale is not being consistently applied. Inconsistent application of rationales leads to very poor language design, confusing authors ("why is X possible but not the almost identical Y?" is a common question in such cases).
  • 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.