checkpoint commit removing PWA / service workers

ayanova/devdocs/todo.txt

@@ -2,10 +2,50 @@
 @@@@@@@@@@@@@@@ ROADMAP STAGE 4 - REPORTING / DASHBOARD / KPI
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
+bugbug: menu won't drop down top right when running ayanova from a local win64 server build
+	started happening in build alpha 25, didn't happen before that so not related to the .net update, more likely something to do with the pwa changes made recently
+	I've actually seen this briefly multiple times during development and it goes away with a refresh IIRC
+	
+	TRY:
+		first TRY does it happen when I run it from localhost development server with remote client or just the windows build server?
+			YES!!!!
+		
+		Try the "whitelisted modules" fix: https://github.com/vuetifyjs/vuetify/issues/5518
+			nope
+		try updating all client bits again
+		something around this? https://vuetifyjs.com/en/features/treeshaking/#vuetify-loader
+		Put a dummy dropdown menu in the toolbar beside the notification icon to rule out my complex menu building code in app.vue
+		Try vue devtools to inspect it from here on Joyce's server to see if anything is visibly related
+		
+		Try putting a development build of client on local server then load and see if it still an issue
+		TRY Can use v7 laptop to use dev tools to investigate on my own computer or vice-versa
+		TRY revert all recent changes one by one until hit on the culprit
+		fuck it would have been nice to have an old w64 build around to test directly, maybe keep them in sequnce for a while
+	NOT 
+		a manifest pwa related issue because I'm seeing it direct browsing from desktop browser, not app version
+			holup, not sure what this means, it seems to be not true
+
+	ISSUE
+		Turns out it's because it's not https secure connection
+		browsers will trust localhost but not aything else
+		serviceworkers will not work on a non secure, non localhost connection
+
+	RESOLUTION
+		Some kind of certificate faking locally on private network server 
+		adapt the client to not use a service worker on a private network (bypass pwa stuff)
+
+	
+
+
 
 BUGBUG: decimal control displays blank even when value comes from server.  It's ok when you manually enter but reverts to blank even though the value is there on open
 	very flakey all around, seems bug riddled, needs thorough testing and fixing
 
+todo: chrome "Lighthouse" test against devops and implement recommendations
+	particularly favor time to first 
+	change .png to .webp 
+
+
 ### SMALL QUICK ITEMS #####
 todo: known issues has some efficiency settings for themes and good stuff to know, check it: https://github.com/vuetifyjs/vuetify/releases/tag/v2.3.0#user-content-known-issues
 todo: new logos too small on large login, add a 3rd (large) size of logo to login form for xl size display
@@ -14,7 +54,7 @@ todo: is notifynewcount request double sending?  It seems like it appears twice
 todo: login button can be obscured by footer, this should not happen try forcing margin below, footer maybe has a setting to confine it?
 	move the login button?
 	make sure enter works with it
-	
+
 todo: scaffold a new vue project with same options and see what it generates for all the config files etc
 	I might be missing some new stuff that needs to be in there in light of the webpack whitelist thing earlier