-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an Observer API #51
Comments
Proposal by Google folks: https://github.com/dmurph/indexed-db-observers Moz's tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1059724#c1 (and full proposal) |
The mozilla link is actually to the full mozilla proposal. |
FYI - the explainer above is not up to date. We want to remove the transaction feature, and add batching of changes. |
TPAC 2019 Web Apps Indexed DB triage notes: Moving from V3 until any implementer has more certainty about a timeline for implementing. |
Any updates? |
On the backburner. We need a partner to run an origin trial with to prioritize this again. |
Hello from 2021 and we still don't have this feature :) Note that Google Firestore actually implemented their own cross tab communication system handle notifications. Not sure how they did it. |
flash, flash : https://github.com/WICG/indexed-db-observers/blob/gh-pages/EXPLAINER.md Experimental |
any news on this topic ? |
Any updates yet? |
Waiting for this |
@burtonator I did the same for RxDB with the BroadcastChannel API. Because BroadcastChannel is widely supported since 2022, I think most use cases for IndexedDB observer can be solved by just emitting BroadcastChannel events across browser tabs. |
Change-tracking events for synchronizing. Basically we need to figure out what primitives we need to provide to allow applications to build synchronizing of IndexedDB databases.
Threads:
The text was updated successfully, but these errors were encountered: