Remove wildcard handling from text-scanner entirely#2241
Merged
Kuuuube merged 1 commit intoyomidevs:masterfrom Nov 11, 2025
Merged
Remove wildcard handling from text-scanner entirely#2241Kuuuube merged 1 commit intoyomidevs:masterfrom
Kuuuube merged 1 commit intoyomidevs:masterfrom
Conversation
Casheeew
approved these changes
Nov 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Somewhat of a followup to #2145
#2145 fixes wildcard scanning making lookups super laggy on normal webpages. But they can still be messed up when using the popup to hover words on the search page.
The search page does not even use this setting to determine whether or not to search using wildcards. In theory it may have been possible to scan
*わfor example on a webpage and have that be a wildcard search. But this is silly and nobody complained when I removed this behavior in #2145 so it makes sense to just remove this entirely.I'm not removing the wildcard setting itself since it probably should control the function on the search page (currently it does nothing). I'll leave that to a future pr.
This does not change any behavior with how the search page handles wildcards.