libdweb custom protocols do not have self-consistent principal
Categories
(WebExtensions :: Experiments, defect, P3)
Tracking
(Not tracked)
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:
- Create a custom protocol with the
libdweb
protocol handler API. - Navigate to a page on that protocol.
- Access
localStorage
orindexedDB
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.
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•1 year ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE
.
For more information, please visit BugBot documentation.
Description
•