[web-db] avoid database init on app start on Safari
ClosedPublic
Actions

Authored by kamil on Jun 6 2023, 10:20 AM.

Details

Reviewers

michal
tomek

Commits

rCOMM85723467d32c: [web-db] avoid database init on app start on Safari

Summary

In general, we establish database connection immediately after app start, on Safari we need to wait for encryption key generated from main thread.
(context)

Depends on D8123

Test Plan

Database should be inited from sqlite-data-handler.js

Diff Detail

Repository

rCOMM Comm

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

kamil created this revision.Jun 6 2023, 10:20 AM

kamil held this revision as a draft.

Herald added a subscriber: ashoat. · View Herald TranscriptJun 6 2023, 10:20 AM

kamil added a child revision: D8125: [web-db] restore database Safari support.Jun 6 2023, 10:21 AM

Harbormaster completed remote builds in B20061: Diff 27491.Jun 6 2023, 10:39 AM

kamil published this revision for review.Jun 7 2023, 1:52 AM

kamil added inline comments.

web/database/database-module-provider.js
38 ↗	(On Diff #27491)	Naming might be confusing, but at this point database is not supported (we don't have a key to it), it will be supported after main thread will provide encryption key

tomek accepted this revision.Jun 13 2023, 4:31 AM

tomek added inline comments.

web/database/database-module-provider.js
37 ↗	(On Diff #27491)	Can we have a const instead of a function that tells if it is Safari? We can avoid having to detect the browser multiple times, as this fact doesn't change through the lifetime of the app.