No validation error is displayed when the Direct Link starts with storageexplorer:///

[v-xianya]

Storage Explorer Version

1.41.1

Regression From

Not a regression

Architecture

arm64

Storage Explorer Build Number

20260311.4

Platform

All

OS Version

Windows 11 arm64/Windows 11 x64/MacOS Sequoia 15.6.1/Linux Ubuntu 22.04

Bug Description

When opening the Open Direct Link dialog:

Entering a link starting with storageexplorer:/ correctly triggers the validation error
“Direct link must start with 'storageexplorer://'”.

However, entering a link starting with storageexplorer:/// does not trigger the validation error and is accepted.

Resource Types

No response

Authentication Method

None

Connection Type

None

Steps to Reproduce

1. Expand a storage account → Blob Containers.
2. Right-click a blob container and select Copy Direct Link to Blob Container.
3. Go to File -> Open Direct Link.
4. Modify the copied link by changing storageexplorer:// to storageexplorer:///.
5. Paste the modified direct link into the Direct link field.
6. Check whether a validation error is displayed.

Actual Experience

No validation error is displayed

Expected Experience

A validation error is displayed

Additional Context

No response

[craxal]

@v-xianya Is the triple slash really invalid? At least one deep link handler allows for it. And based on your screenshot, it looks to be correct. Since the dialog doesn't block, what happens if you accept it? Does the link work correctly? Or does some other error occur?

[v-xianya]

@craxal Using "///" will not result in an error and can successfully proceed to the next step. can successfully attach to or navigate to containers without errors.

[craxal]

I notice the triple shash is not flagged if a SAS link is used. No error is shown, so that can get confusing. I think what needs to happen here is we need better validation within the dialog itself.