I know this has been referred to in other topics but they appear they have been closed without a resolution from Firefox. This problem is one of the many reasons users should not take the updates that Firefox forces upon you: too many problems incorporated which take too long to fix. It took me a long while to find a working method which Firefox wouldn't broadcast, but I got there in the end. Google just doesn't update, it broadcast the changes well in advance allowing developers to adapt before the roll out. Developers who don't work for Firefox that is! I had stopped updates as they make more problems than they fix, but had to try the latest as Google maps stopped working: All I get is a blank webpage with nothing showing. Others have suggested a plugin etc. etc. etc., but this does not solve the fact that other browser don't have this problem and neither does Firefox! What! You read this right! version 52.0 works without a hitch with Google maps, so a way of getting Firefox to work is to revert to a previous version which doesn't have the dodgy embedded code. So why exactly are we waiting for an update for something that has worked in the past but has now stopped because the developers either don't know how to fix it or can't be bothered. Firefox are clearly showing they are not coping with updates as well as the competition. I use the term loosely, as Firefox appear to have given up entirely!