Opened 17 years ago
Closed 16 years ago
#7655 closed enhancement (wontfix)
Code view should reflect output
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.6.1 |
Component: | TinyMCE | Keywords: | needs-patch |
Focuses: | Cc: |
Description
Currently, if I enter the following into the visual editor
Here’s a paragraph.
And another…
(So that there is a blank line between the two) and then switch to "code" view, then all I see is this -
Here’s a paragraph.
And another…
Exactly the same as I just typed into the visual editor. However, that's not the code that gets published when I hit publish. The code that gets published is this -
<p>Here’s a paragraph.</p> <p> </p> <p>And another…</p>
Should the "code" view not actually show the code that's going to be sent to the browser in the finished article? (I.E. the p tags and the entity codes?)
Change History (7)
#4
@
16 years ago
IMO, Code view shouldnt be showing <p> tags, as thats added on output by wpautop(), Should the code view expand shortcodes? Should it show what the output will be once plugins filter it? etc.
In my mind, The code view is for entering html manually ie. not tinymce, its not designed to reflect the output of the blog post, rather, its the input of the blogpost.
Also, this isnt really TinyMCE.. The code view is not tinyMCE.. soo..
+1, definitely. I find the current behaviour very irritating.
But actually the code that gets published should be
(i.e. Without the empty pair of
p
tags between the two 'real'p
s. The blank line is interpreted as the end of one paragraph and the start of the next, whilst a single line break would just insert abr
tag.)I don't know which is currently generated, but that's what it should be.