[wp-trac] [WordPress Trac] #44958: &nbsp character in title generates a permalink (and slug) with space

[WordPress Trac]

#44958: &nbsp character in title generates a permalink (and slug) with space
-------------------------------------------------+-------------------------
 Reporter:  ace2_heart                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Permalinks                           |     Version:  4.8
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-test-info has-         |     Focuses:
  screenshots needs-unit-tests dev-feedback      |
-------------------------------------------------+-------------------------
Changes (by SirLouen):

 * keywords:  needs-testing has-patch has-test-info has-screenshots needs-
     unit-tests => has-patch has-test-info has-screenshots needs-unit-tests
     dev-feedback


Comment:

 Replying to [comment:39 dmsnell]:
 > The smaller patch here proposes fixing one very specific incarnation of
 a broader bug, and unfortunately at the current time introduces more
 breakage (and so I think it would be best to ensure that if we merge it,
 we fix that remaining issue before doing so).

 I entirely agree with you: this is a fix for this bug. A fix that has
 scaled to sort more potential troubles, but after all a generalization fix
 for this bug. Hence, this should stay here.

 This said, as sometimes happens, these kinds of fixes are entirely made on
 the head of the patch builder, that lose momentum without documenting all
 use-cases for such fix. Recently
 [https://make.wordpress.org/test/2025/05/15/building-the-testing-use-case/
 I posted this in Test Blog], to discuss the need of use-cases (not only
 code, but also, text-written cases to understand what is the scope of the
 patch that is being built), which happens this patch to be the case.

 Again, since this report has completely lost all the momentum, and still,
 the bug exists, I would propose the following:

 1. Given that we already have test reports that are already passing
 [https://core.trac.wordpress.org/attachment/ticket/44958/44958.diff for
 the former patch] I would simply pass, merge and ship it.

 2. Afterward, I would open a new ticket, for the enhancement as suggested
 whenever @dmsnell feels with the motivation to resume his patch. In the
 new ticket, `test-info` or a use case should be provided, and the new code
 to be reviewed (and optionally `unit-tests`).

 3. Anyway, I would not fully close this ticket, to leave the possibility
 to add `unit-cases` subsequently.

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