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
The reason these headers are required for sqlite/OPFS is because they use SharedArrayBuffer, which requires them. (ref 1 1, ref 2)
However, in Chrome extensions, SharedArrayBuffer works without those headers, so sqlite/OPFS are usable. (ref 4)
Unrelated to OPFS, there was an issue on the Firefox bug tracker regarding SharedArrayBuffer usage within extensions two years ago, which culminated in only allowing it for privileged extensions (aka not available to normal people like us). (ref 3)
其他:
不在fire extension环境下访问该地址,会提示The OPFS is available.说明OPFS可用。
原理为在Request Response Header里添加了以下参数:
问题未解决,该问题已经在2021年的mozilla上的论坛被提出。
Mozilla issues
https://bugzilla.mozilla.org/show_bug.cgi?id=1673477
相关资料:
https://discourse.mozilla.org/t/sqlite-and-opfs-not-working-in-firefox-extension/111667
引用djahandarie 的回答:
其他:
不在fire extension环境下访问该地址,会提示The OPFS is available.说明OPFS可用。
原理为在Request Response Header里添加了以下参数:
相关资料见:https://github.com/sqlite/sqlite-wasm?tab=readme-ov-file#in-a-worker-with-opfs-if-available
The text was updated successfully, but these errors were encountered: