Not able to use "regex:" match

[harshalgithub]

As most of the technologies are SAAS based, then the Hostname is common always and only some identification ID is changing in the URL, which in-turn changes the environment as well.

For Example:

Main Domain: https://www.rootdomain.com/

Env 1: https://www.rootdomain.com/css/xys/**identification-code-1234**/welcome

Env 2: https://www.rootdomain.com/css/xys/**identification-code-5678**/welcome

Env 3: https://www.rootdomain.com/css/xys/**identification-code-349980-23-3435-4565444**/welcome

So here I tried the below regex in extension settings, but after saving the configuration, it does not work. I have the latest Chrome version (Version 139.0.7258.67 (Official Build) (64-bit))

regex:www.rootdomain.com/css/xys/01974612-ba31-727c-b266-b26051191234/welcome/

regex:^http(s)?.www.rootdomain.com/./01974612-ba31-727c-b266-b26051191234/.*

regex:^http(s)?.www.rootdomain.com/.css/xys/01974612-ba31-727c-b266-b26051191234/welcome/.

But somehow it's not working. It's only working based on the hostname value, which is not correct in above scenario as hostname always common across.

Can someone suggest how to use regex in SAAS environment URLs for environment identifications.

Please let me know if I am missing something. Or regex feature is not enabled yet.

[harshalgithub]

Also, how to use "Added support for ribbon transparency." feature, I can't see any configuration option

I have highlighted regex which I tried to use in above comment

[harshalgithub]

@geovanneb anything I am missing above, Thank you

[sebastian-bartkowiak]

@harshalgithub I found the root cause of the issue. It's because (for reason unknown to me) when you use regex match it's tested against window.location.hostname, and not window.location.href as is the case for regular matches. you can find the relevant piece over here
Would be happy to prepare the PR changing this behavior if @geovanneb feels it's ok, and this is actually still maintained?