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

Bug 22232 - Introduce replacement elements now so that we will be able to replace recycled elements in the future
Summary: Introduce replacement elements now so that we will be able to replace recycle...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P3 enhancement
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-01 07:22 UTC by Ian Yang
Modified: 2015-06-26 05:36 UTC (History)
5 users (show)

See Also:


Attachments

Description Ian Yang 2013-06-01 07:22:55 UTC
Hi editors,

As you may have heard about that many developers don't quite like the idea of recycling old elements such as u, i, b, and small.

So the proposal here is introducing replacement elements as early as possible. The reason to do so is to make HTML5 elements more semantics and standardized. And it's not like we should keep using u, i, b, and small forever.

Introducing replacement elements, while temporarily keep the recycled elements, can make browsers start to implement replacement elements. Once all browsers have implemented all replacement elements, we can safely remove those recycled elements from HTML5 spec.

Some suggestion of replacement elements are:

For u (a span of text with an unarticulated, though explicitly rendered, non-textual annotation), we can introduce something like <annot>.

For i (a span of text in an alternate voice or mood, or otherwise offset from the normal prose in a manner indicating a different quality of text), we can introduce something like <alt>.

For b (a span of text offset from its surrounding content without conveying any extra emphasis or importance, and for which the conventional typographic presentation is bold text), we can introduce something like <offset>.

For small (represents side comments such as small print), we can introduce something like <note>.

Of course, the above mentioned naming of replacement elements might not be the best. The idea here is aim to make browsers being prepared with replacement elements as early as possible so that we can safely drop the recycled elements from HTML5 spec as early as possible.


Sincerely,
Ian Yang
Comment 1 Michael[tm] Smith 2015-06-16 11:46:27 UTC
Resolved as lacking any indication of implementer interest nor any indication of interest among webdevs.
Comment 2 Michael[tm] Smith 2015-06-17 02:46:42 UTC
The best way to pursue this would be first take it back to some other discussion forum or WG (e.g., the whatwg mailing list, or the public-webapps list, or discuss.webplatformorg) then re-open it if/when there's any new info.