Just a follow up in case anyone watching this ...
op had move site from http to https and had done search and replace in the DB to correct all internal links to the moodle. The setups of Google Oath (and probably Facebook) require that a 'developer' (the op) register a project and setup a credentials API for use. When the ops site was http the call back and javascript roots were correct and the buttons showed as they should. When site changed to https, the op hadn't gone back to those sites (Google/Facebook) and changed the call backup/javascript roots from http to https. Thus, FireFox, would display as an icon indicating a fully secure site to one of 'some content not secure' - in other words there was a mix of http and https on the page. One had to allow/override the settings for the https page in Firefox to allow the non-https content (the buttons that had http call backs) to display.
Fixed. Op went back into configs of those API's, changed call backs etc. from http to https.
'spirit of sharing', Ken