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
Following on from #1123, a "universal" messaging solution could be provided without altering the DOM in the messaging channel by leveraging the global appState object. At various points in the back end, this object can be updated to show the loading state. If using libzim (#870), then the state would be updated in the interface between app.js and the libzim worker, but messaging would be more limited as we don't have an API to report on the internal libzim decoding state.
The text was updated successfully, but these errors were encountered:
@asmit27rai This isn't a good first issue. There are lots of complexities to it, and it involves a change of architecture for the app. So I strongly suggest you select another issue.
Following on from #1123, a "universal" messaging solution could be provided without altering the DOM in the messaging channel by leveraging the global
appState
object. At various points in the back end, this object can be updated to show the loading state. If using libzim (#870), then the state would be updated in the interface betweenapp.js
and the libzim worker, but messaging would be more limited as we don't have an API to report on the internal libzim decoding state.The text was updated successfully, but these errors were encountered: