Short summary
Built-in app browser truncates URL query strings on auto-launch and intercepts/blocks standard left-click link navigation.
Affected version or release
0.2.10
Installation context
Local desktop client installation.
What happened?
When a local process or background task auto-launches a URL into an internal app browser tab, the application wrapper completely strips out the query string parameter from the address. This breaks token-based authentication links (like local dashboard logins).
Additionally, once a web page is rendered inside the built-in browser view, standard left-clicks on hyperlinks are completely unresponsive. Clicking a link does not navigate or open a new view unless you explicitly right-click the link and select "Open link in new window" from the context menu. This issue happens consistently across different web pages and local services running inside the app browser workspace.
Steps to reproduce
No response
Expected behavior
-
Run a local task or orchestration process [egs: aspire start] in the terminal that auto-opens a web link containing a query token (e.g., https://localhost:54812/login?t=e1564eec6cb811e295aaa0269ac7af78).
-
Observe the auto-opened tab's address bar: the query string parameters are missing, truncating the URL to just the base address (e.g., https://localhost:54812/).
-
On the loaded web page, attempt to left-click any standard text or navigation hyperlink.
-
Note that the left-click is intercepted or ignored. Right-click the link to open the context menu and select "Open link in new window" to force it to navigate.
Additional context
No response
Short summary
Built-in app browser truncates URL query strings on auto-launch and intercepts/blocks standard left-click link navigation.
Affected version or release
0.2.10
Installation context
Local desktop client installation.
What happened?
When a local process or background task auto-launches a URL into an internal app browser tab, the application wrapper completely strips out the query string parameter from the address. This breaks token-based authentication links (like local dashboard logins).
Additionally, once a web page is rendered inside the built-in browser view, standard left-clicks on hyperlinks are completely unresponsive. Clicking a link does not navigate or open a new view unless you explicitly right-click the link and select "Open link in new window" from the context menu. This issue happens consistently across different web pages and local services running inside the app browser workspace.
Steps to reproduce
No response
Expected behavior
Run a local task or orchestration process [egs: aspire start] in the terminal that auto-opens a web link containing a query token (e.g., https://localhost:54812/login?t=e1564eec6cb811e295aaa0269ac7af78).
Observe the auto-opened tab's address bar: the query string parameters are missing, truncating the URL to just the base address (e.g., https://localhost:54812/).
On the loaded web page, attempt to left-click any standard text or navigation hyperlink.
Note that the left-click is intercepted or ignored. Right-click the link to open the context menu and select "Open link in new window" to force it to navigate.
Additional context
No response