Make WordPress Core

Opened 17 years ago

Closed 16 years ago

#6490 closed defect (bug) (wontfix)

Shift-enter in <li> causes <p>

Reported by: novasource's profile novasource Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3.3
Component: TinyMCE Keywords:
Focuses: Cc:

Description

If I am in a list item (<li>), and I press shift-enter, the resulting tag should be a <br>.

If I press shift-enter twice, the resulting tags should be <br><br>.

Instead, WordPress is entering <p> tags.

E.g., here's what I should get:

<li>Text text text text.
<br>
<br>Text text text text.</li>

Instead, I get this:

<li>Text text text text.
<p>Text text text text.</p></li>

Change History (7)

#1 follow-up: @ionfish
17 years ago

Surely two newlines should produce this:

<li>
<p>Text text text text.</p>
<p>Text text text text.</p>
</li>

#2 in reply to: ↑ 1 @novasource
17 years ago

  • Component changed from General to TinyMCE
  • Version set to 2.3.3

Replying to ionfish:

Surely two newlines should produce this:

<li>
<p>Text text text text.</p>
<p>Text text text text.</p>
</li>

I think that for that to be valid, the default list code would have to be <li><p>Text text text text.</p></li>.

Simply translating shift-enter to <br> seems more straightforward.

#3 @azaozz
17 years ago

  • Component changed from TinyMCE to General

This is how the js version of wpautop currently works, it sees 2 <br /> as 2 new lines '\n\n', so makes a <p>.

#4 @matt
16 years ago

  • Component changed from General to TinyMCE
  • Milestone changed from 2.7 to 2.8

#5 @janeforshort
16 years ago

  • Milestone changed from 2.8 to Future Release

Punting to be evaluated in next development cycle due to time constraints.

#7 @Denis-de-Bernardy
16 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Should be sent upstream to TinyMCE

Note: See TracTickets for help on using tickets.