[wp-trac] [WordPress Trac] #63426: wptexturize breaks markup
WordPress Trac
noreply at wordpress.org
Thu May 15 00:01:27 UTC 2025
#63426: wptexturize breaks markup
-------------------------------------------------+-------------------------
Reporter: madhazelnut | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Formatting | Version: 6.6.2
Severity: normal | Resolution:
Keywords: wptexturize needs-patch dev- | Focuses:
feedback |
-------------------------------------------------+-------------------------
Changes (by SirLouen):
* keywords: wptexturize needs-patch => wptexturize needs-patch dev-
feedback
Comment:
In today's `test-triage` we were discussing if `wptexturize` uses were
being taken too far, maybe. Judging by the docs, it's difficult to
understand the scope of this function. It appears that it's open for too
many use cases. You can use `wptexturize` from a whole HTML document to
just for a paragraph (ranging from maximum complexity to something
relatively trivial)
@oglekler was suggesting that current exclusions are still very loose. So,
for example, `iframe` should be, by default, in the list of exclusions
(`default_no_texturize_tags`)
I'm still not convinced for such exclusion, but I believe that docs should
consider better explaining the scope of this function. Is it really
intended to be a Swiss army for text styling almost any doc given? Or its
better intended to just over trivial scenarios?
Probably the looseness of this function is the main reason of the chain of
tickets related to `wptexturize`. Adding `dev-feedback` for further
discussion about this topic.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63426#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list