indexedDB on Edge doesn't support putting null values

Issue #106663 • Assigned to Shawn P.

Details

Created
Apr 27, 2014
Privacy
This issue is public.
Found in build #
0.0011
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL = http://www.w3.org/TR/IndexedDB/#value-construct

URL:

Repro Steps:

<< store.put("item", null)

Invalid argument.

Expected Results:

null values should be supported.
as on specification, we should be able to store objects that can be stored using the HTML5 structured cloning algorithm, which means storing objects: http://www.w3.org/TR/IndexedDB/#value-construct
since null is a primitive value (not even an object) we should be able to store nulls

Actual Results:

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “IPBS P.”

      Changed Assigned To from “IPBS P.” to “Bruce M.”

      Changed Assigned To to “Kamen M.”

      Changed Assigned To from “Kamen M.” to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Shawn P.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Shawn P.” to “Ali A.”

      Changed Status from “Confirmed”

      Changed Assigned To from “Ali A.” to “Shawn P.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Won’t fix”

      Changed Assigned To to “Shawn P.”

      Changed Status from “Won’t fix”

      Changed Status to “Needs root cause”

      Changed Status from “Needs root cause”

      Changed Title from “indexedDB on IE doesn't support putting null values” to “indexedDB on Edge doesn't support putting null values”

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

    Sign in