Tested on 108.0.1.

STR:

1. Visit https://bugzilla.mozilla.org.
2. Open Find in Page and search for alternative. Confirm that this triggers a "Phrase not found".
3. Click on New Account on the web page.
4. Without changing the search term, click on the up/down arrow to trigger another search.
5. There should only be one single match for the search term alternative.

Expected Beahavior:

"Reached end/top of page, continued from top/bottom" is not in bold.

Actual Behavior:

"Reached end/top of page, continued from top/bottom" is in bold when the search only returned a single match. Repeatedly clicking on the up/down arrow does not make it disappear. The above STR is not reproducible if the search term returned more than one match (e.g.Thunderbird).

This is not 100% reproducible but you should see it after one or two tries.

mozregression --bad 91 --pref browser.proton.enabled:true returned

Last good revision: 7bff3dc37b071d5272e2d445a0bfcbe21aabd38d (2021-03-22)
First bad revision: ea38e210ba4d6d14f40cd17fc38515ce7e965e60 (2021-03-23)
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7bff3dc37b071d5272e2d445a0bfcbe21aabd38d&tochange=ea38e210ba4d6d14f40cd17fc38515ce7e965e60
Switching bisection method to taskcluster
...
There are no build artifacts for these changesets (they are probably too old).

Presumably this is related to bug 1690334?

The Bugbug bot thinks this bug should belong to the 'Core::CSS Parsing and Computation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

(In reply to aoia7rz7l from comment #0)

Presumably this is related to bug 1690334?

Sounds extremely likely

The severity field is not set for this bug.
:enndeakin, could you have a look please?

For more information, please visit auto_nag documentation.