Make WordPress Core

Opened 6 years ago

Closed 5 years ago

#42830 closed defect (bug) (wontfix)

Automatic List coding error

Reported by: wordaspect's profile Wordaspect Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.9.1
Component: TinyMCE Keywords:
Focuses: Cc:

Description (last modified by swissspidy)

With TinyMCE Advanced Version 4.6.7 occurs an error in coding while switching between visual and text editor

Step 1) writing in visual editor and assigning listing to boh lines:

* topic 1
* topic 2

Step 2) results in corrct coding in text editor

    <ul>
        <li>topic 1</li>
        <li>topic 2</li>
    </ul>

Step 3) insrting a break and a space in the visual editor after “topic 1”

* topic 1

* topic 2

Step 4) and switching to the text editor gives also a correct code, even so the “<br> ” is deleted:

    <ul>
        <li>topic 1</li>
        <li>topic 2</li>
    </ul>

Step 5) but switching afterwards back to the visual code results in a weard coding and the text editor has following to show:

    <ul>
        <li style="list-style-type: none">
    <ul>
        <li>topic 1</li>
    </ul>
    </li>
    </ul>
    <ul>
        <li>topic 2</li>
    </ul>

These works always like this with the mentioned steps above.

Change History (4)

#1 follow-up: @swissspidy
6 years ago

  • Description modified (diff)

#2 in reply to: ↑ 1 @Wordaspect
6 years ago

Replying to swissspidy:
Thank you, for the next time I know it better ;)

#3 @azaozz
6 years ago

  • Milestone changed from Awaiting Review to Future Release

Hi @Wordaspect, thanks for the bug report.

Confirmed, happens only when the caret is in the <li> element or some text in there is selected and you add a <br> at the end of the <li>, and there are no other characters after it.

#4 @azaozz
5 years ago

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

This is a rare edge case in the "keeping the caret position" code and is now superseded by the block editor. Closing as wontfix, feel free to reopen (preferably with a patch) if this still needs fixing in the classic editor.

Note: See TracTickets for help on using tickets.