STR

1. Go to https://todomvc.com/ and open the devtools debugger
2. Select https://todomvc.com/site-assets/main.js
3. Do Ctrl/Cmd + F to open file search
4. Search for this (there should be around 17 entires). Moving through the search should work nicely
5. Select https://todomvc.com/bower_components/jquery/dist/jquery.js (Make sure the file search is still open)

What happened?

The search results does not update after the source is switched. And cycling through the search results is broken.

What should have happened?

A search results should update to match the current source selected.

This probably regressed by Bug 1962417

Set release status flags based on info from the regressing bug 1962417

Backed out for causing failures at browser_dbg-search-file-retains-query.js..

Backout link: https://hg-edge.mozilla.org/integration/autoland/rev/ea530ec099aac8b9172137208a59e59e3bda68c6

Push where failures started: https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=dQZtML4GR5usv3izkZ9lZg.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&searchStr=linux%2C18.04%2Cdebug%2Cmochitests%2Ctest-linux1804-64-qr%2Fdebug-mochitest-devtools-chrome%2Cdt10&revision=67baceb379aeddc2c4490ca806b6fe41921b5b3e

Failure log: https://treeherder.mozilla.org/logviewer?job_id=512708967&repo=autoland&lineNumber=8589

https://hg.mozilla.org/mozilla-central/rev/8fb6b0c2f4d1

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

• If yes, please nominate the patch for beta approval.
  • See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
• If no, please set status-firefox140 to wontfix.

For more information, please visit BugBot documentation.

Original Revision: https://phabricator.services.mozilla.com/D253015

Comment on attachment 9495427 [details]
Bug 1971094 - [devtools] Update search results when the selected source changes r=#devtools

:bomsy, beta is closed since we are in RC week for Fx140. This will ride the train to beta with Fx141.
I changed the target repo of your uplift revision to release.

We could take it in a ride along, but that depends on the uplift request. Please add the request form to in Phabricator.

:bomsy, beta is closed since we are in RC week for Fx140. This will ride the train to beta with Fx141.
I changed the target repo of your uplift revision to release.

Sounds good! Thanks!

We could take it in a ride along, but that depends on the uplift request. Please add the request form to in Phabricator.

Not too clear what i need to do here, can you help clarify?

Uplift requests need some details to give context around risk, etc.
You can add it to the phabricator revision, see the following for some instructions:
https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift#Submit_the_Uplift_Request_Form

firefox-release Uplift Approval Request

• User impact if declined: Devtools debugger user will see wrong search results while switching source during a file search
• Code covered by automated testing: yes
• Fix verified in Nightly: yes
• Needs manual QE test: no
• Steps to reproduce for manual QE testing: -
• Risk associated with taking this patch: Low risk
• Explanation of risk level: Just javascript code change to do a search when the source changes
• String changes made/needed: -
• Is Android affected?: no

Set release status flags based on info from the regressing bug 1962417