“No apps installed that can open about:blank”

[hadess]

Maybe we should just drop those requests to the floor?

[hadess]

This was triggered by the BlueJeans application, not sure why.

[Mikenux]

You have marked BlueJeans as EOL. Is this problem still relevant? "about:blank" seems like something a web browser opens...

[smcv]

about: is a URI scheme like any other, so I don't really see a reason for it not to be treated the same as every other URI scheme: if a web browser wants to offer it, it can register for x-scheme-handler/about.

(But Firefox and Chromium don't, so I don't know what BlueJeans was aiming to achieve by this.)

[Mikenux]

Sorry, I forgot to specify that "about:" is something that web browsers handle internally, like "about:config". After a bit of research, a blank page appears when no homepage is configured, in the event of a connection problem, incorrect URL, ... (see for example https://geekflare.com/aboutblank-in-chrome-firefox-safari/ ). So maybe BlueJeans tried to open a URL, failed to resolve it, then tried to open it by sending "about:blank", but didn't have a built-in web browser to handle it. The right thing to do for apps that try to open a URL when they don't have a built-in web browser is to ask to open the original URL (http://...), at least if it's not an incorrect link given by another person or a misconfiguration of something.

[Mikenux]

Maybe related? #1202