New issue
Advanced search Search tips

Issue 719053 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 10
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Tracking: IDB wasm serialization behavioral difference between browsers

Project Member Reported by mtrofin@chromium.org, May 5 2017

Issue description

This tracks this behavioral difference - we should try and reach consensus with the other browsers.
 
Specifically, Chrome will reject storing WASM modules to IndexedDB in non-secure contexts.
Project Member

Comment 2 by bugdroid1@chromium.org, May 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bd4b16652f605ec91c76c7026efc75fdb9b8079b

commit bd4b16652f605ec91c76c7026efc75fdb9b8079b
Author: Mircea Trofin <mtrofin@chromium.org>
Date: Sat May 06 18:43:01 2017

[wasm] TODO & tracking bug for IDB behavioral difference.

Bug:  chromium:719053 
Change-Id: Ic4eec1ca6e3c9d723d19c5661fe196c092762808
Reviewed-on: https://chromium-review.googlesource.com/497970
Commit-Queue: Mircea Trofin <mtrofin@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#469837}
[modify] https://crrev.com/bd4b16652f605ec91c76c7026efc75fdb9b8079b/third_party/WebKit/Source/modules/indexeddb/IDBObjectStore.cpp

Status: Archived (was: Untriaged)
Archiving P3s older than 1 year with no owner or component.

Sign in to add a comment