Both previous match number and "Phrase not found" are displayed for a short period of time
Categories
(Toolkit :: Find Toolbar, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | unaffected |
firefox107 | + | verified |
firefox108 | --- | verified |
People
(Reporter: emilghitta, Assigned: eemeli)
References
(Regressed 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
240.67 KB,
image/gif
|
Details | |
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta+
|
Details | Review |
Found in
- Firefox 107.0b2 (BuildId:20221018185850)
Affected versions
- Firefox 108.0a1 (BuildId: 20221018213916)
- Firefox 107.0b2 (BuildId:20221018185850)
Tested platforms
- Affected platforms: Windows 10 64bit, macOS 11 & Ubuntu 22
Steps to reproduce
- Access the following webpage.
- Hit ctrl + f.
- Type "enf".
- Hit enter or click on the ^ V (find in previous or find in next).
Expected result
- The "Phrase not found" is displayed.
Actual result
- Both "1 of 8 matches" (which comes from the "en" search) and the "Phrase not found" strings are displayed for a second.
Regression range
- This seems to be a regression. Will provide asap.
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Using mozregression it pointed to https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a94ad0477229c32639861e6ae0d4367150a3e713&tochange=a2f1f50e1a972f57d269b6a0eaba51d3f01bfe62
Regressor bug 1792464 - Convert findbar.properties to Fluent
Comment 2•2 years ago
|
||
The bug is marked as tracked for firefox107 (beta). However, the bug still isn't assigned and has low severity.
:yshash, could you please find an assignee and increase the severity for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 3•2 years ago
|
||
I was not able to come up with solid automated test for these changes, as that would need to rely on catching the DOM in the middle of a couple of async updates.
Some checkbox/statuslabel updates are included here, as the previous implementation was producing console warnings.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 4•2 years ago
|
||
:enndeakin, seems :eemeli is on PTO until RC week. Could you or someone else review/land this patch?
Pushed by earo@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0c70b459ca9e Fix remaining flashes of invalid content in findbar status. r=NeilDeakin
Comment 6•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Assignee | ||
Comment 7•2 years ago
|
||
Comment on attachment 9299732 [details]
Bug 1796078 - Fix remaining flashes of invalid content in findbar status. r=NeilDeakin!
Beta/Release Uplift Approval Request
- User impact if declined: Some incorrect text may be very briefly visible to users when using the findbar
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Very small change affecting only the findbar status indicator
- String changes made/needed:
- Is Android affected?: No
Comment 8•2 years ago
|
||
Comment on attachment 9299732 [details]
Bug 1796078 - Fix remaining flashes of invalid content in findbar status. r=NeilDeakin!
Approved for 107.0b9
Comment 9•2 years ago
|
||
bugherder uplift |
Updated•2 years ago
|
Updated•2 years ago
|
Reporter | ||
Comment 10•2 years ago
|
||
This issue is verified fixed using Firefox 107.0b9 (BuildId:20221103190044) and Firefox 108.0a1 (BuildId:20221103214316) on Windows 10 64bit, Ubuntu 22.04 and macOS 11
Comment 11•1 year ago
|
||
clearing need info as this has been assigned / fixed
Description
•