Hello Gmaximus! It has been a busy few weeks.
I have been testing the overall functionality with the cache and have identified some issues:
1- When the cache is turned off, the manifest cannot be reached. This prevents users from installing the web app because the browser cannot access the manifest information.
Should caching be an isolated functionality? This could prevent changes to the cache and future work on that component from affecting the functionality of the entire module. A sub module maybe?
2- When the cache is turned on, there are some issues with cache refresh when updates occur. For example, after updating a regular node, the cache should delete the old cached information so that the browser fetches the latest content.
3- haven't tested the logout functionality yet
Active
1.71
Code
It was a little disappointing not hearing back from you on the last issue.
I appreciate your input.
I admit I haven't checked editing a node but I did test new comments being posted.
I literally had a couple of mins yesterday. I found the manifest worked in either case.
I'll spend time investigating your issue. I should be able to work on this next week.