The custom header requirement will make this version of sqlite unusable for many usecases. Can SQLite fallback to using slower persistant APIs if neither Cross-

The custom header requirement will make this version of sqlite unusable for many usecases. Can SQLite fallback to using slower persistant APIs if neither Cross-Origin-Opener-Policy or Origin-Embedder-Policy are set? If not, does the SQLite project intend to provide a version that would? Devs who don't need the high performance but want wider compatibility will probably continue to use the "unofficial" versions. Also, last I checked, you could definitely load web assembly in a page that has a File:/// origin.