Make WordPress Core

Opened 15 months ago

Closed 3 months ago

#23321 closed defect (bug) (wontfix)

ins button in text editor produce semantically different HTML then the U button at the visual editor

Reported by: mark-k Owned by:
Milestone: Priority: normal
Severity: minor Version:
Component: Editor Keywords:
Focuses: Cc:


U button at the visual editor makes something like

<span style="text-decoration: underline;">text</span>

while the ins at the text editor makes

<ins datetime="2013-01-30T05:44:49+00:00">text</ins>

It is actually not easy to understand that the intentions behind both are equivalent - underline the text*, but semantically they have different meaning, and in the context of WP usage the styling one has probably the more correct meaning.

Alternatively, if "ins" is important html tag then why it is not possible to add it in the visual editor.

related #20149

*Browsers by default underline "ins" but twentyeleven and twentytwelve remove it.

Change History (1)

comment:1 azaozz3 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Right, underline and <ins> are two different things. The Text editor is targeted at the "power users". If they want to use <ins>, they can. The Visual editor doesn't have "ins" by default, can be added by a plugin.

Note: See TracTickets for help on using tickets.