Promote find replace dialog to production

[lukstbit]

Purpose / Description

This was discussed and I think we should do it.

From the linked issue:

• left a TODO for the ui improvements
• the ViewModel can and will come at a later point

Later edit: wondering if we should add to the dialog a warning about the (potential) destructive effects of using the dialog.

Fixes

• Fixes Productionize 'Find & Replace' #19929

How Has This Been Tested?

The dialog appears without having to enable the dev setting.

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[ZornHadNoChoice]

Later edit: wondering if we should add to the dialog a warning about the (potential) destructive effects of using the dialog.

I agree, it's fine even if there's a second confirmation dialog since it's not something you do often.

But just to confirm: those effects would be due to user error, like using .* regex, right?

[lukstbit]

I was thinking more about a warning label for the user about creating a backup using #20644. If the user does this he has a restore point independent of the undo queue and I think it would be enough. I wouldn't oppose a dialog asking to confirm the use of a regex, but I don't like the multiple dialogs stacking(I'm not happy at all when navigating the custom study dialogs stack).

See:

[david-allison]

Could we defer this to 2.25?

This is a fair risk to add in at the start of the beta cycle

[lukstbit]

Could we defer this to 2.25?

Sure. I added it because it was requested :)
But if we add the backup menu option and the notice above, we kind of did enough to provide users with safety IMO.

[criticalAY]

Looks clean, thankyou

[david-allison]

Sure. I added it because it was requested :)

Ahaa, sorry about that, too close for comfort now. Definitely want to give this one a good soak in alpha

[lukstbit]

Besides the original code, I added two more changes:

• a warning in the dialog like in the image above
• an entry for TR.browsingFindAndReplace in TR.sentenceCase and used that instead

[david-allison]

• Updated strings from Crowdin 2026/05/07 16:08 #20980

[github-actions]

Maintainers: Please Sync Translations to produce a commit with only the automated changes from this PR.

Read more about updating strings on the wiki,

• localization-administration
• download-localized-strings