[wp-trac] [WordPress Trac] #30644: "wpautop" Enhancements

[WordPress Trac]

#30644: "wpautop" Enhancements
---------------------------------+---------------------
 Reporter:  stefanrz             |       Owner:  (none)
     Type:  enhancement          |      Status:  new
 Priority:  normal               |   Milestone:
Component:  Formatting           |     Version:
 Severity:  normal               |  Resolution:
 Keywords:  wpautop 2nd-opinion  |     Focuses:
---------------------------------+---------------------
Changes (by khag7):

 * keywords:  wpautop => wpautop 2nd-opinion


Comment:

 There are 39 open tickets that the proposed feature plugin above would
 either fix immediately or put us most of the way towards fixing. I'll list
 the 39 if you'd like, but for now just take my word for it.

 I recognize this is 6 years old. I recognize this is not as desirable now
 as it was prior to Gutenberg. I recognize that the 39 open tickets to fix
 wpautop are not a high priority. I recognize that any new version of
 wpautop needs to maintain back compat. But despite all that, I'd like to
 try to understand if there's a desire to fix this and if so, what steps
 need to be taken.

 As far as I can understand, designing some unit tests would be the first
 step. If I were to do so (and I'd likely need some help with example
 content) I'd end up with several dozen tests that fail on the current
 wpautop function. What is step two? Make the current wpautop pluggable and
 replace with the feature plugin from the previous comment and then test
 again? Lets say we get to a point where we pass all our tests. Does this
 even get implemented or is this too likely to be a breaking change for
 users? How do we test against that?

 Tagging @azaozz as you maintain Formatting and I'd really like your
 guidance on this. Is this likely to succeed? Is this desirable?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/30644#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform