Opening browser causes a change in the window title

[thany]

When opening a browser tab, the title of the window where the process runs, changes to Windows PowerShell.

This is undesirable, because:

1. It's too generic to recognize on the task bar among other command prompt windows.
2. The application had changed it priorly to something meaningful, in my case.

This problem was first reported in #16192 @ Storybook.

TLDR: there is no way to change it back to what I meant for it to be, and there shouldn't need to be a way if better-opn left the window title alone.

[michaellzc]

Please see my response at #37 (comment)

[thany]

This issue is not specific to Storybook, better-opn - if I read the source code correctly - literally opens powershell.exe to open a browser tab. Just don't? 🤷🏻‍♂️ You don't need powershell just to open a browser tab.

If I type on the command prompt:

start https://duckduckgo.com

It will open a tab in my favourite/default browser to go there. Job done. This doesn't need X-many different approaches on Windows.

This will solve similar problems in other packages as well. Not just Storybook.

(In hindsight, I shouldn't have mentioned Storybook maybe. I imagine you took it as reporting a problem here, that existed there, but this problem is NOT specific to Storybook, just to get that clear as day)

[michaellzc]

better-opn is created to do one thing and one thing only (that solved my pain point when working on some side projects with GatsbyJS gatsbyjs/gatsby#6550), reuse browser tab on macOS otherwise fallback to the upstream open package. I do not intent or have the bandwidth to maintain a fork of open and implement new features.

Therefore, what you're proposing is out of the scope this project. Would you kindly move the discussion into the upstream open project instead?

[thany]

So you're saying on Windows and Linux, better-opn simply doesn't need to exist? That does confirm my finding that I've never seen it reusing any browser tab.

This might be important to know for users of this package.

But even so, I do like to know: why bother with powershell? If this is a macOS-minded package, why do you bother with a Windows feature that isn't even needed?