mirror of
https://github.com/servo/servo.git
synced 2025-09-15 01:18:22 +01:00
fc3feceee5
- Use sqlite instead of heed. (one indexed database = one sqlite database) - Implement the backend for indexes - Use keyranges where needed (as specified by the spec) - Implement `getKey` - Fix channel error messaging (led to a bunch of changes to how async requests are handled) Note: `components/net/indexeddb/engines/sqlite/serialize.rs` is unused; I can delete it if needed. Testing: Switching to sqlite eliminated many panics (exposing some new failures). Fixes: #38040 --------- Signed-off-by: Ashwin Naren <arihant2math@gmail.com>
105 lines
2.9 KiB
INI
Vendored
105 lines
2.9 KiB
INI
Vendored
[idb-binary-key-roundtrip.any.worker.html]
|
|
[Binary keys can be supplied using the view type Uint8Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Uint8ClampedArray]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Int8Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Uint16Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Int16Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Uint32Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Int32Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Float16Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Float32Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Float64Array]
|
|
expected: FAIL
|
|
|
|
[ArrayBuffer can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[DataView can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[DataView with explicit offset can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[DataView with explicit offset and length can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[Uint8Array with explicit offset can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[Uint8Array with explicit offset and length can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
|
|
[idb-binary-key-roundtrip.any.html]
|
|
[Binary keys can be supplied using the view type Uint8Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Uint8ClampedArray]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Int8Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Uint16Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Int16Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Uint32Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Int32Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Float16Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Float32Array]
|
|
expected: FAIL
|
|
|
|
[Binary keys can be supplied using the view type Float64Array]
|
|
expected: FAIL
|
|
|
|
[ArrayBuffer can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[DataView can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[DataView with explicit offset can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[DataView with explicit offset and length can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[Uint8Array with explicit offset can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
[Uint8Array with explicit offset and length can be used to supply a binary key]
|
|
expected: FAIL
|
|
|
|
|
|
[idb-binary-key-roundtrip.any.serviceworker.html]
|
|
expected: ERROR
|
|
|
|
[idb-binary-key-roundtrip.any.sharedworker.html]
|
|
expected: ERROR
|