Open Bug 1591351 Opened 2 years ago Updated 2 years ago

libdweb custom protocols do not have self-consistent principal

Categories

(WebExtensions :: Experiments, defect, P3)

defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: sam, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

  1. Create a custom protocol with the libdweb protocol handler API.
  2. Navigate to a page on that protocol.
  3. Access localStorage or indexedDB in the console.

(Extension to reproduce: https://github.com/sammacbeth/libdweb-protocol-bugs)

Actual results:

For localStorage: Quota originNoSuffix (moz-nullprincipal:{948a55e1-6c93-4153-b353-68d5df20a0a9}) doesn't match passed one (test://origin/)!: ActorsParent.cpp:6077

For indexedDB: same errors as above, plus IndexedDB UnknownErr: IDBFactory.cpp:134

Expected results:

Storage APIs should be usable in custom protocol pages.

This comment (https://bugzilla.mozilla.org/show_bug.cgi?id=1493002#c3) points to these errors being caused by the protocol not having a self-consistent principal.

See Also: → 1493006

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.