[Chrome] Provider not injected to local files

I noticed there is no way to use Casper Wallet directly from local files:

If this is expected, please add some information about it.

[Comp0te]

Hi, thanks for the report - this is expected behaviour rather than a bug.

Casper Wallet's content script (which injects the CasperWalletProvider) is intentionally scoped to web origins only. In our manifest the content scripts match
["http:///", "https:///"], so pages served from file:// are deliberately excluded.

There are two reasons for this:

• Injecting a wallet provider into arbitrary local files is a security concern - any HTML file opened from disk would gain access to the provider.
• Chrome additionally requires the user to manually enable "Allow access to file URLs" per-extension for any file:// interaction, which we don't rely on.

If you're developing a dapp locally, please serve it over http://localhost (e.g. npx serve, Vite/webpack dev server, etc.) - the provider will be injected there as normal.

Closing as working-as-intended, but happy to reopen if there's a specific use case we're missing.