You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,11 +212,11 @@ Here's a comparison of fake-indexeddb and real browser IndexedDB implementations
212
212
<!-- wpt_results_total=1651 -->
213
213
| Implementation | Version | Passed | % |
214
214
| --- | --- | --- | --- |
215
-
| Chrome | 143.0.7475.0 | 1651 | 100% |
215
+
| Chrome | 143.0.7476.0 | 1651 | 100% |
216
216
| Firefox | 146.0a1 | 1498 | 90.7% |
217
-
| Safari |229 preview | 1498 | 90.7% |
217
+
| Safari |230 preview | 1498 | 90.7% |
218
218
| Ladybird | 1.0-62c00712fa | 772 | 46.8% |
219
-
| fake-indexeddb | 6.2.3| 1368 | 82.9% |
219
+
| fake-indexeddb | 6.2.4| 1368 | 82.9% |
220
220
<!-- wpt_results_end -->
221
221
222
222
Keep in mind that these tests include a lot of edge cases (such as rare error conditions), so even hitting ~40% likely means that the core IndexedDB functionality is covered. Your app will probably work fine.
0 commit comments