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
In the lack of Preference API in ts-toolkit, user preferences (and ReadiumCSS) have to use methods that are left exposed but will no longer be public once the Preference API is added.
For instance, frameManager.msg to inject ReadiumCSS properties into iframes’ html, or nav.pool.setPerPage to select the number of pages to display in FXL.
These should obviously be migrated once the Preference API is available.
The text was updated successfully, but these errors were encountered:
In the lack of Preference API in ts-toolkit, user preferences (and ReadiumCSS) have to use methods that are left exposed but will no longer be public once the Preference API is added.
For instance,
frameManager.msg
to inject ReadiumCSS properties into iframes’html
, ornav.pool.setPerPage
to select the number of pages to display in FXL.These should obviously be migrated once the Preference API is available.
The text was updated successfully, but these errors were encountered: