WordPress.org

Make WordPress Core

Opened 10 months ago

Last modified 2 months ago

#50499 new enhancement

Slug field should not autocorrect in Quick Edit view

Reported by: swb1192 Owned by:
Milestone: 5.8 Priority: normal
Severity: normal Version: 5.5
Component: Quick/Bulk Edit Keywords: has-patch
Focuses: Cc:

Description (last modified by afragen)

When using the Quick Edit view on a Posts admin page, autocorrect is enabled when editing the slug. This may result in the unintended slugs.

By using spellcheck="false" in the input field, browsers including Safari will no longer autocorrect or spell check the slug field.

Attachments (1)

0000.diff (646 bytes) - added by swb1192 10 months ago.
spellcheck disabled for slug field

Download all attachments as: .zip

Change History (5)

@swb1192
10 months ago

spellcheck disabled for slug field

#1 follow-up: @SergeyBiryukov
10 months ago

Hi there, welcome to WordPress Trac! Thanks for the ticket and the patch.

Just noting that per MDN web docs, spellcheck="false" appears to be the correct value to disable the check, rather than spellcheck="off".

#2 in reply to: ↑ 1 @swb1192
10 months ago

Replying to SergeyBiryukov:

Hi there, welcome to WordPress Trac! Thanks for the ticket and the patch.

Just noting that per MDN web docs, spellcheck="false" appears to be the correct value to disable the check, rather than spellcheck="off".

Thanks for catching that! I wrote "off" in the description erroneously, but the patch has the correct "false".

#3 @afragen
10 months ago

  • Description modified (diff)

#4 @SergeyBiryukov
2 months ago

  • Milestone changed from Awaiting Review to 5.8

Just noting that spellchecking was previously enabled for the post title field on Edit Post screen in classic editor, see [30350] / #30338. That appears to be the only instance of the spellcheck attribute in core at the moment.

This ticket suggests disabling it for the post slug field in Quick Edit on Posts screen.

I don't have a strong preference either way here, moving to the milestone for discussion.

Last edited 2 months ago by SergeyBiryukov (previous) (diff)
Note: See TracTickets for help on using tickets.