Assembler: Fix the action bar stuck

[arthur791004]

Related to #83034

Proposed Changes

• The action bar might be stuck there when you hover off the pattern. The reason is the device-switcher__frame element is removed & appended to the DOM whenever the value of the hasSelectedPattern changes. And it leads to the mouseleave event on the device-switcher__frame element cannot be triggered anymore.
• Here is the real case on production (chrome only) but I cannot reproduce it on my local env
  • When you land on the Assembler with the selected pattern at the beginning (e.g.: refresh the page), the hasSelectedPattern is false initially, and we bind the mouseleave event to the device-switcher__frame element. However, the value becomes true immediately so the mouseleave event doesn't work as that element will be removed from the DOM and then appended again.

Testing Instructions

• Go to the Assembler
• Select a pattern, remove it, and select it again
• Hover on that pattern and ensure you see the action bar
• Hover off that pattern and ensure the action bar will be gone instead of sticking there

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• https://wpcalypso.wordpress.com/devdocs/docs/testing/index.md for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-85588

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-85588&env=jetpack

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~21 bytes added 📈 [gzipped])

name         parsed_size           gzip_size
import-flow        +43 B  (+0.0%)      +21 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[taipeicoder]

👍