Blob-Workers can't access IndexedDB

Issue #5942817 • Assigned to Ali A.

Details

Created
Dec 21, 2015
Privacy
This issue is public.
Reports
Reported by 6 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

This example shows a Worker, successfully accessing IndexedDB, using an external script: http://bl.ocks.org/nolanlawson/863e464f3025d7199a1f

This example shows a similar Worker, failing to access IndexedDB, using a Blob (url): http://bl.ocks.org/bemson/57dffb89ee7b28d63a29 With dev-tools, you can see how the Blob-Worker example throws an exception when attempting to open a database connection.

Expected Results:

Workers should have access to IndexedDB.

Blob-workers should share the same privileges as their host/owner context’s origin.

Actual Results:

Dev Channel specific:

No

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Mara P.”

      Changed Assigned To to “Rico M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Ali A.”

    • I can confirm this bug still exists in 15010.1002. The error is “Unable to get property ‘open’ of undefined or null reference” indicating that self.indexedDB is undefined for blob-workers.

    • Can you confirm if the issue still exists?

    • Microsoft Edge Team

      Changed Assigned To from “Ali A.” to “James M.”

      Changed Assigned To from “James M.” to “Ali A.”

    • It is almost 17 months since this bug was raised. Can you please confirm if it has been fixed yet?

    • Can any one confirm, if this issue is fixed? This issue has been reported in 2015 and still not resolved.

    You need to sign in to your Microsoft account to add a comment.

    Sign in