Address bar filled with random "URL"

[Hatedia]

Hello,

I have noticed on both, Google Chrome and Microsoft Edge when I install the extension and start the browser, new tab is empty, however the address bar always has this weird random "URL". Would it be possible to adjust it to start with empty address bar? Attaching screenshot for better explanation.

Thank you.

[zmni]

weird random "URL"

That random url is the extension id. If you visit the addon page on Edge addon store, you'll see it has the same random URL.

extension url issue

I can't reproduce this issue. I don't use chrome so I've only tested it on Edge stable and dev version, and it's works fine on my end. What Edge version do you use?

screenshots

Added.

[Hatedia]

I had it on the last version of Edge/Chrome and it has been present. In this and previous versions as well.

[zmni]

I stll can't reproduce this, tested it on version 83.0.478.44 (Stable), 85.0.531.1 (Dev) and 85.0.537.0 (Canary). All without problems, working as it should. Have you tried it with only this extension installed? It might be conflict with other extensions.

[SumatraPeter]

I just installed and tested 1.2.4 on ChrEdge 86.0.622.69 (Stable) and I can confirm that sometimes, seemingly at random, the Address Bar does get populated with that URL when the browser is launched after previously closing all windows and waiting for background processes to exit.

To test just close all open ChrEdge windows and then relaunch the browser after a while. After a few attempts you'll most likely notice this issue. I just can't tell what's triggering it however.

[luukatyuo]

Hi there, i can reproduce this with edge / latest version / stable.
This happens if u close ALL open Tabs, even the last one. After starting edge again it will give the url with the exention-id

edit: what i use as a workaround is using the edge-option for searching via adressbar, so i can insta type where i wanna go 2.

[zmni]

This looks like a Microsoft Edge bug, it is extremely difficult to reproduce, even now I still can't reproduce this issue. I will try to report it to Microsoft, hopefully they can reproduce and find out what caused this to happen.

Thanks for the report.