At the very least, if you are navigating between routes, the column widths should be remembered in a service. LocalStorage would be nice on a per/computer basis.
This may only be workable for tables that declare an ID or ref-id since we'll need a constant "key" to cache on.
At the very least, if you are navigating between routes, the column widths should be remembered in a service. LocalStorage would be nice on a per/computer basis.
This may only be workable for tables that declare an ID or ref-id since we'll need a constant "key" to cache on.