[wp-trac] [WordPress Trac] #42340: Spurious Insertion of <p>aragraph Tags
WordPress Trac
noreply at wordpress.org
Mon Oct 30 14:54:23 UTC 2017
#42340: Spurious Insertion of <p>aragraph Tags
--------------------------+------------------------------
Reporter: oeconomist | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Formatting | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
--------------------------+------------------------------
Comment (by JPry):
Replying to [comment:6 oeconomist]:
> It is one thing for the code to recognize that most users don't know or
don't want to be bothered with mark-up, and therefore to interpret
newlines as paragraph closures; it's another for the code to infer that a
user didn't intend the mark-up that he or she entered.
The WordPress editor and {{{wpautop()}}} work the way they do because most
people don't want be bothered with markup. WordPress Core is designed for
the majority, and the majority of users would want their markup to be
cleaned up if they copied and pasted it from some other source. That means
that for the majority of users, the current behavior is '''not''' a bug.
For those users, like yourself, who know exactly what markup they want, it
is certainly understandable that the default behavior has aspects that
don't work for you. However, that means that the best solution for you may
be to disable the default behavior.
> But they are just work-arounds, not patches of the bug.
One thing that hasn't been mentioned yet here is that even though this
seems like a small change, this could have huge ramifications for the
majority of users. They would suddenly have different generated output on
their site. To them, if the change you're requesting was made, the ''new''
behavior would be a bug.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/42340#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list