Make WordPress Core

Opened 18 years ago

Closed 17 years ago

Last modified 17 years ago

#3311 closed defect (bug) (wontfix)

Visual rich editor doesn't handle HTML correctly (linebreaks,  , &lt, >, &, IFRAME)

Reported by: ceefour's profile ceefour Owned by: andy's profile andy
Milestone: Priority: low
Severity: minor Version: 2.0.4
Component: TinyMCE Keywords:
Focuses: Cc:

Description

Too numerous to mention actually. I've posted several stuff in WordPress Forum labeled "[BUG]" (and tagged "bug" as well).

Paste the attached code into visual editor's HTML editor.

Then click "Save and Continue", again (twice). You should see that the texts are now joined together, not properly line-break-ed. <p> is now gone.

---

<table width="100%">

<tr>

<td>

<p><strong>Mozilla Firefox 2.0</strong></p>
<p>Browser terbaru yang sangat handal.</p>
</td>

<td>

<p><strong>Internet Explorer 7.0</strong></p>
<p>Browser dari Microsoft yang telah banyak mengalami perbaikan.</p>
</td>

</tr>

</table>

Change History (8)

#1 @Viper007Bond
18 years ago

  • Component changed from General to Administration
  • Milestone changed from 2.0.5 to 2.1
  • Priority changed from high to low
  • Severity changed from major to minor

Changing to low priority because HTML is best entered via the standard editor. ;)

#2 @matt
18 years ago

  • Milestone changed from 2.1 to 2.2

#3 @foolswisdom
18 years ago

  • Milestone changed from 2.2 to 2.3

#4 @Nazgul
18 years ago

  • Component changed from Administration to TinyMCE
  • Owner changed from anonymous to andy

#5 @znuff
18 years ago

<p> and </p> are automatically removed because wordpress has the autop() feature that automatically adds paragraph tags wherever it's logical to do so ;-)

#6 @ryan
17 years ago

  • Milestone changed from 2.3 to 2.4

#7 @thee17
17 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

This bug is really old and little traction. Closing as won't fix. Reopen with patch or if need be.

#8 @Nazgul
17 years ago

  • Milestone 2.5 deleted
Note: See TracTickets for help on using tickets.