This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Back to bug 11915

Who When What Removed Added
webmaster 2011-01-30 18:44:50 UTC CC webmaster
Summary Suggestion: Instead of forbidding <u> and inventing <mark> you could as well redefine <u> to be what <mark> is intended for -- roughly the same idea as for <i> and <b>. Clearly not all old HTML4 <i> / <b> / <u> match what the new HTML5 <i> / <b> / <mark> Suggestion: Instead of forbidding <u> and inventing <mark> you could as well redefine <u> to be what <mark> is intended for -- roughly the same idea as for <i> and <b>. Clearly not all old HTML4 <i> / <b> / <u> match what the new HTML5 <i> / <b> / <mark>
ian 2011-02-19 00:18:43 UTC Status NEW RESOLVED
CC ian
Resolution --- WONTFIX
mike 2011-08-04 05:04:39 UTC Component HTML5 spec (editor: Ian Hickson) LC1 HTML5 spec (editor: Ian Hickson)

Back to bug 11915