servoshell: Align console behavior for shell and double‑click launches - #43010

Won't this still spawn the console, so you'll get this "flashing console window that immediately disappears" effect when starting via GUI?

Won't this still spawn the console, so you'll get this "flashing console window that immediately disappears" effect when starting via GUI?

It is much better as the issue #40996 fixed is much more severe.

This also allows: seeing the follow-up stdout/stderr, if started executable from console.
Also on my machine, I do not see any flash, even on a slow debug build.

Video can explain better.

My main concern is that I believe the original decision (when production builds just had no output at all) was AFAIK made to avoid exactly that blinking, since it could be "suspicous" to users. So I think this PR might need wider review, to ensure there is consensus.
I'd personally be fine with the change, if we documented it in the book (in an FAQ / common issues section perhaps).

🔨 Triggering try run (#22660422044) for Windows

✨ Try run (#22660422044) succeeded.

it could be "suspicous" to users.

I honestly find current console output behaviour much more suspicious as shown in videos.
For this PR, I can't see any pop-up in the release build (FreeConsole happens extremely fast). As a daily Windows user, I do see a bunch of apps with a console window open for a few seconds during launch tho... Windows users are even used to that😅

Maybe this can be discussed in Zulip.

IIRC that is related to shell somehow. I think using bash (from git-windows) works as expected (like on linux).

With that being said, I support this change as I find this inconsistent unexpected.

Any chance we can advance this?
I get multiple servoshell binaries and run them in console directly to see different debug logs.
Right now this makes it more difficult :(

Someone thinks this change could be added to the monthly blog post! To help with this, we need someone to answer the following questions: 😄

1. Who is most impacted by this change: users, Servo developers, embedders, or some other group?
2. What observable difference does this change make?
3. What preferences (if any) need to be enabled to observe this difference?
4. What (if any) specific URLs are affected?

If this change is part of a broader feature/project please make sure the PR description contains a Fixes: #12345 or Part of: #12345 issue reference.

Please add @servo-highfive monthly update answer when answering these questions so the bot notices your answer (or just quote this comment).

Thanks for helping us prepare the monthly blog post! ❤️

I will get back to this bot message after figuring out what's the new label about

We have a new monthly update label, which make it easier for the people writing the monthly blog-post to include noteworthy additions, if the contributor shortly explains what the PR is about. Since you already posted videos in the comment above, and it affects windows users, I thought this might be fitting (although in the end the blog post author decides what to include)

@servo-highfive monthly update answer

1. Who is most impacted by this change: users, Servo developers, embedders, or some other group?
   Servo developers, users.

2. What observable difference does this change make?
   Video can explain better.

3. What preferences (if any) need to be enabled to observe this difference?
   Running on Windows machine.

4. What (if any) specific URLs are affected?
   All.