Closed Bug 1981925 Opened 4 months ago Closed 4 months ago

The searched string is not cleared after using Show in folder context menu option inside the Library

Categories

(Toolkit :: UI Widgets, defect)

Desktop
All
defect

Tracking

()

VERIFIED FIXED
143 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox-esr140 --- unaffected
firefox141 --- wontfix
firefox142 --- verified
firefox143 --- verified

People

(Reporter: atrif, Assigned: emilio)

References

(Regression)

Details

(Keywords: nightly-community, regression, ux-mode-error)

Attachments

(1 file)

  • This is only a follow-up since this was initially found by Alice in bug 1979434

Found in

  • 142.0b8

Affected versions

  • 142.0b8
  • 143.0a1 (2025-08-08)
  • 141.0.3

Tested platforms

  • Affected platforms: Ubuntu 24, Windows 10, macOS 12
  • Unaffected platforms: none

Steps to reproduce:

  1. Open Library
  2. Type search term (e.g., f) in Search field and hit [ENTER]
  3. Right-click on a search result
  4. Choose Show in folder
  5. Click on the Search field to focus
  6. Hit [ENTER]

Actual result:

  • Nothing happens

Expected result:

  • Clear search term at step 4 like previous version.

Regression window:

QA Whiteboard: [qa-found-in-c142] [S3] → [qa-found-in-b142] [S3]

:emilio, since you are the author of the regressor, bug 1967209, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)
Blocks: 1981968
Flags: needinfo?(emilio)

That gets the right behavior. I filed bug 1981968 because this seems a
bit footgunny to me.

Assignee: nobody → emilio
Status: NEW → ASSIGNED
Pushed by agoloman@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/b8a9b3dbbc76 https://hg.mozilla.org/integration/autoland/rev/b7483c08e439 Revert "Bug 1981925 - Use input.clear() for places searchbox. r=places-reviewers,Standard8" for causing build bustages.

Backed out for causing build bustages.

Flags: needinfo?(emilio)

Could you reland? Fairly sure it's not the culprit

Flags: needinfo?(emilio) → needinfo?(agoloman)
Flags: needinfo?(agoloman)
Severity: -- → S3
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch

The patch landed in nightly and beta is affected.
:emilio, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)

Comment on attachment 9505963 [details]
Bug 1981925 - Use input.clear() for places searchbox. r=#places-reviewers

Beta/Release Uplift Approval Request

  • User impact if declined/Reason for urgency: One-liner
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: comment 0
  • List of other uplifts needed: none
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): One-liner.
  • String changes made/needed: none
  • Is Android affected?: No
Flags: needinfo?(emilio)
Attachment #9505963 - Flags: approval-mozilla-beta?
Flags: qe-verify+

Comment on attachment 9505963 [details]
Bug 1981925 - Use input.clear() for places searchbox. r=#places-reviewers

We are in RC week and out of betas so moving request to release for the next dot release or a re-spin if possible.

Attachment #9505963 - Flags: approval-mozilla-beta? → approval-mozilla-release?
QA Whiteboard: [qa-found-in-b142] [S3] → [qa-found-in-b142] [S3][uplift][qa-ver-needed-c143/b142]

Verified fixed with Firefox 143.0a1 (2025-08-13) on Windows 10x64, macOS 15 and Ubuntu 24 using steps from comment 0.

QA Whiteboard: [qa-found-in-b142] [S3][uplift][qa-ver-needed-c143/b142] → [qa-found-in-b142] [s3] [uplift] [qa-ver-done-c143/b142]

Comment on attachment 9505963 [details]
Bug 1981925 - Use input.clear() for places searchbox. r=#places-reviewers

Approved for 142.0.1

Attachment #9505963 - Flags: approval-mozilla-release? → approval-mozilla-release+

I was able to reproduce the issue with an affected Firefox Nightly 143.01 build from 2025-08-07 on macOS 14, as described in Comment 0.
Verified as fixed using Firefox 142.0.1-build1 on macOS 14, Windows 11 and Ubuntu 22.04.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: