With version 50 of Chrome, the geolocation API requires websites to use a secure origin (https). See this ArcGIS Blog Post. My experience testing this out is that unless I serve the application with https, then the geolocate button in the WAB won't work in Chrome. I've changed all the references for my resources in my WAB application to use https. The only remaining "mixed content" warnings that I get from the browser are the Open Street Map images that are being requested by the Enhance Basemap gallery widget.
Example: The page at 'https://xyz.webapbuilder' was loaded over HTTPS, but requested an insecure image '