Repository: facebook/react
Pull request: [DevTools][standalone] Stop sending highlight events when a component is selected

<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->
The change only applies to standalone and brings the behavior in sync with the browser extension.
In https://github.com/facebook/react/pull/25106/files, we started to send new highlight events when a component is hovered, which is consistent with the browser extension. But in the browser extension, we don't keep highlighting a selected component. It was also causing some bad DX on RN, because there is no easy way to unselect an element.
The devtools frontend is also sending this `inspectElement` event every second when an element is selected, so removing the listener can also saves some CPU.


## How did you test this change?

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->
Synced to a RN app locally, no highlight is shown anymore on a selected element.

Changed files:
filename: packages/react-devtools-core/src/backend.js
patch: @@ -131,21 +131,6 @@ export function connectToDevTools(options: ?ConnectOptions) {
         }
       },
     });
-    bridge.addListener(
-      'inspectElement',
-      ({id, rendererID}: {id: number, rendererID: number, ...}) => {
-        const renderer = agent.rendererInterfaces[rendererID];
-        if (renderer != null) {
-          // Send event for RN to highlight.
-          const nodes: ?Array<HTMLElement> = renderer.findNativeNodesForFiberID(
-            id,
-          );
-          if (nodes != null && nodes[0] != null) {
-            agent.emit('showNativeHighlight', nodes[0]);
-          }
-        }
-      },
-    );
     // $FlowFixMe[incompatible-use] found when upgrading Flow
     bridge.addListener(
       'updateComponentFilters',