07-07-2022, 02:52 PM
(This post was last modified: 07-12-2022, 06:19 PM by MJS@mjs.us.)
Back to the back button - I observed this while testing Datatables with large datasets where a data pull took 0.5 to 1 seconds. This is noticeable enough where I can't use the new back button functionality quite yet.
1. Access IWForm+DataTables [populated by Content Handler] by GoToURL, datatables refreshes once correctly.
2. Back button to an IWForm then forward button to IWForm+DataTables, datatables refreshes twice incorrectly.
3. Add an address to the url bar of a static page or non IW app and navigate to it.
4. Back button to IWForm+DataTables, datatables refreshes once correctly.
Navigating to IWForm+DataTables by GoToURL always works correctly.
Navigating to IWForm+DataTables from a static or non IW site by back/forward buttons always works correctly.
Navigating to IWForm+DataTables from an IWForm by back/forward buttons causes double calls to content handler.
Extra test: DataTables in a static page served by an IW app Content Handler always works correctly with back/forward buttons.
1. Access IWForm+DataTables [populated by Content Handler] by GoToURL, datatables refreshes once correctly.
2. Back button to an IWForm then forward button to IWForm+DataTables, datatables refreshes twice incorrectly.
3. Add an address to the url bar of a static page or non IW app and navigate to it.
4. Back button to IWForm+DataTables, datatables refreshes once correctly.
Navigating to IWForm+DataTables by GoToURL always works correctly.
Navigating to IWForm+DataTables from a static or non IW site by back/forward buttons always works correctly.
Navigating to IWForm+DataTables from an IWForm by back/forward buttons causes double calls to content handler.
Extra test: DataTables in a static page served by an IW app Content Handler always works correctly with back/forward buttons.

