Dashboard Window in Automa Shrinks and Becomes Inaccessible After Closing

[MauricioLucas]

Title: Automa Extension Dashboard Disappears After Resizing and Cannot Be Restored After Closing

Bug description After installing the Automa extension on Google Chrome, Chromium, and Brave browsers on Linux Mint, the Automa window opens maximized, hiding the browser behind it. When clicking and dragging the title bar to make it a floating window, the window resizes to almost imperceptible dimensions—about 1 or 2 pixels wide and 15 pixels high, appearing as a small white line on the screen. From this point on, the extension works, but if the Dashboard window is closed, it cannot be reopened by any means (clicking Home in the dropdown menu, using the shortcut, disabling and enabling the extension, or restarting the browser). The only way to restore it is to remove and reinstall the extension, causing the loss of all edited automations.

Reproducing the error Steps to reproduce the behavior:

1. Install the Automa extension on Google Chrome, Chromium, or Brave on Linux Mint.
2. Open the Automa Dashboard.
3. Click and drag the title bar to make it a floating window.
4. Observe the window resizing to almost imperceptible dimensions.
5. Close the Dashboard window.
6. Attempt to reopen the Dashboard by various means.

Expected behavior The Automa Dashboard window should open in a visible and usable size, and it should be possible to reopen the Dashboard after closing it without reinstalling the extension.

Desktop:

• OS: Linux Mint
• Browser:
  • Google Chrome Version 126.0.6478.114 (Official Build) 64-bit
  • Brave Version 1.67.119 Chromium: 126.0.6478.114 (Official Build) 64-bit
  • Chromium Version 125.0.6422.112 (Official Build) for Linux Mint 64-bit
• Extension Version: (Please provide the version of the Automa extension you are using. You can find this information in the browser's extensions page.)

Additional context I have tested all possible options and installed the extension on other Chrome-based browsers, and they all showed the same error. I installed the extension on Firefox, and it works correctly, but this browser is not an option for my automations because I would have to start from scratch and find many alternatives.

Error Details from Inspect Element The following error details were obtained using the right-click + Inspect on the home icon of the extension:

Error: Invalid value for bounds. Bounds must be at least 50% within visible screen space.
    at popup.bundle.js:30:49382
<button role="button" class="ui-button relative h-10 transition bg-input p-2 rounded-lg" title="Dashboard" vtooltip=""><span class="flex h-full items-center justify-center"><svg viewBox="0 0 24 24" fill="currentColor" height="24" width="24" class="v-remixicon" xmlns="http://www.w3.org/2000/svg"><!----><g><path fill="none" d="M0 0h24v24H0z"></path><path fill-rule="nonzero" d="M13 19h6V9.978l-7-5.444-7 5.444V19h6v-6h2v6zm8 1a1 1 0 0 1-1 1H4a1 1 0 0 1-1-1V9.49a1 1 0 0 1 .386-.79l8-6.222a1 1 0 0 1 1.228 0l8 6.222a1 1 0 0 1 .386.79V20z"></path></g></svg></span><!----></button>

document.querySelector("#app > div.mb-6.dark.relative.z-10.px-5.pt-8.text-white.placeholder\\:text-black > div.mb-4.flex.items-center > button:nth-child(5)")

const o = e=>e && "object" == typeof e && "function" == typeof e.then
                          , s = (t,n)=>(...r)=>{
                            e.runtime.lastError ? t.reject(new Error(e.runtime.lastError.message)) : n.singleCallbackArg || r.length <= 1 && !1 !== n.singleCallbackArg ? t.resolve(r[0]) : t.resolve(r)
                        }

Suggested Fix A possible fix might involve ensuring that the window bounds are correctly calculated and enforced within the visible screen space. The error suggests that the bounds need to be at least 50% within the visible screen space.

[MauricioLucas]

Error: Invalid value for bounds. Bounds must be at least 50% within visible screen space.

[MauricioLucas]

Uncaught (in promise) Error: Invalid value for bounds. Bounds must be at least 50% within visible screen space.