[wp-trac] [WordPress Trac] #55117: Possible 5.9 Bug: Unknown character ( or %ef%bf%bc ) on content title

[WordPress Trac]

#55117: Possible 5.9 Bug: Unknown character ( or %ef%bf%bc ) on content title
-------------------------------------------------+-------------------------
 Reporter:  cantuaria                            |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  Permalinks                           |     Version:  5.9
 Severity:  normal                               |  Resolution:
 Keywords:  has-testing-info has-screenshots     |     Focuses:
  has-patch needs-testing                        |
-------------------------------------------------+-------------------------
Changes (by ironprogrammer):

 * keywords:  has-testing-info has-screenshots has-patch => has-testing-info
     has-screenshots has-patch needs-testing


Comment:

 Thanks, @dmsnell!

 === Issue at Hand
 > So for all involved I think there's a conflation of a few different
 issues here:

 Yes, as also [https://core.trac.wordpress.org/ticket/55117#comment:4
 suggested]  [https://core.trac.wordpress.org/ticket/55117#comment:5
 earlier], I agree we should limit the scope of this ticket to the impact
 on slugs, and file separate tickets for when this character is [usually
 unintentionally] stored in the title field, or the encoding update in 5.9
 [https://core.trac.wordpress.org/ticket/55117#comment:8 that was reported]
 to cause 404s.

 As for the slug issue, I've drafted [https://github.com/WordPress
 /wordpress-develop/pull/2937 PR #2937] for consideration, which removes
 the object replacement character (``) from published URLs.

 To clarify what the above PR addresses, there haven't been any suggestions
 to modify general URL-encoding, but to only account for the object
 replacement character (``). Other incidental URL-encoded characters (like
 `ü`) would remain unaffected.

 === Testing Steps
 > Unfortunately I think we need to track a different sequence of steps
 because there's a difference between intentionally entering the object-
 replacement character and the object-replacement character unexpectedly
 appearing in a post title, which I believe is the real problem tracked in
 this issue (but maybe I'm wrong).

 Nope, you're right. Going through [#ticket this ticket] and the
 [https://github.com/WordPress/gutenberg/issues/38637 related Gutenberg
 issue], there has been some difficulty in consistently reproducing this
 problem "naturally", which is why explicit and intentional steps to
 inserting this character can be useful toward thinking about and
 reproducing the unexpected ''results''. (I likes me a good crowbar 😉.)
 But your point is well taken.

 That being said,
 [https://github.com/WordPress/gutenberg/issues/38637#issuecomment-1172678390
 further cross-browser testing] has highlighted the inconsistencies between
 browsers for creating and observing this issue, and I've generated an
 updated set of reproduction steps that focuses only on the impact to
 slugs/URLs. Instructions to follow.

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