[wp-trac] [WordPress Trac] #55052: The tag field hangs the browsers when you have a bunch of tags
WordPress Trac
noreply at wordpress.org
Mon Feb 7 19:58:09 UTC 2022
#55052: The tag field hangs the browsers when you have a bunch of tags
-------------------------------------------------+-------------------------
Reporter: pikamander2 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.9.1
Component: Query | Version: 5.9
Severity: critical | Resolution:
Keywords: has-patch needs-testing 2nd-opinion | Focuses:
| performance
-------------------------------------------------+-------------------------
Comment (by costdev):
I agree and consider the maintenance fix a necessity for 5.9.1.
I also agree that matching Gutenberg's behaviour makes sense. The filter,
whether released in 5.9.1 or 6.0, will allow it to be set to a preferred
value.
> @azouamauriac I'm not really sure if limit the result number is a good
idea, since some result will match but they won't be show up because of
limit.
IMO, there is already a technical limit in the form of the feature
freezing when too many tags exist. This change implements a safety limit
to prevent that ever occurring.
There's at least two ways to do this:
1. Investigate all factors that cause the freeze, from the number of tags,
to the amount of data (long tag names, etc).
2. Set a limit that's consistent with other behaviour in Core.
IMO, setting the limit to `20` makes sense for the following reasons:
1. Consistency in Core.
2. The amount of time it takes a user to enter one or two more characters
to reveal their desired tag is significantly less than scrolling through a
long list of possible matches.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/55052#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list