Trying to diagnose a Google Maps/Safari Issue - google-maps

Our site is able to be accessed through FF/IE/Chrome, etc. however when a user opens the site in Safari, it doesn't load the google maps box. It stays the grey loading color.
We use Google Maps v3 and geolocation to set the default position of the map, and if they deny location or something, we have a fallback to an IP service to center it somewhat close to them. Works everywhere but on Safari (multiple versions). It just hangs.
Any ideas at how I can diagnose this? I'm running Windows 7/XP so it's tough to do.
Thanks!

You can use the firebug lite version
and also have a try with the built-in developer tools.
This thread Debugging javascript in Safari for Windows says more about this.

Related

The google translator icon disappears from my address bar when I load my website

I need to be able to translate my web application into another language. I enabled the google translate extension in chrome. When I load my company website with chrome the translate icon appears and I can translate the site. I then loaded my secure web application in chrome and the translate icon disappeared. My knowledge on how the translator works with web pages in minimal at best. Any help would be appreciated as I do not know where to begin. Any links to helpful articles on how the translator does its job would also be appreciated
I also had a problem with the google translate (gt) icon disappearing from the right side of the Chrome address bar. I believe I caused the problem myself as I was trying to come up with a way to use it to switch languages quickly using Keyboard Maestro.
I keep 2 Chrome windows open with 2 different gmail accounts, and the gt icon was only missing from one of the windows. I tried many things and couldn't get the gt icon to come back.
Eventually, I was able to fix the problem based on the procedure described on this page, which suggests going to this address: chrome://settings/languages to make sure the Offer to translate pages that aren't in a language you read option is on in the Languages section, as shown in this image:
In my case, the option was already set to on. So I turned it off, logged out of the account associated with that Chrome window, closed that browser window, and when I opened a fresh browser window for that gmail account the gt icon was back.
I'm using Chrome Version 96.0.4664.93 on a MacAir (M1, 2020) running MacOS 12.0.1

google docs on firefox: Saving your changes is taking longer than usual. Editing is temporarily disabled

I am attempting to use google docs with firefox, but am constantly getting this message.
It never goes away.
And if I close the tab all of my work is deleted.
This is a brand new Firefox install.
Is this an attempt to force us back to using chrome with google docs?
I have been a chrome user for many years but was recently forced to switch to firefox because chrome has an intolerable bug on macOS catalina.
I need to use google docs but I can't use chrome because of this chrome bug and now I can't use firefox because of this bug with google docs.
Is there a work-around for the problem?
Chrome allows me to work with local copies of google docs without losing work if I lose my network connection, but I cannot find a similar plugin for firefox.
I tried to reproduce the issue on Firefox, however it seems to work fine at my end without any sort of error or warning popup in saving.
But, Google is known to play nasty with competitors to promote Chrome and it can't be ruled out that it might be a cause too. You can try multiple options, and check which one works.
Possible Solutions:
If you want to trick google into thinking you are browsing on Chrome, change this setting in Firefox as mentioned here!
Try using the Firefox Developer Edition: [Official Link])(https://www.mozilla.org/en-US/firefox/developer/ "Firefox Developer Edition")
If the above options don't work, try switching to Microsoft Edge for a Chrome alternative if the bug is particularly associated with Google Chrome, though they both are based on Chromium, it's worth a try.
Searching through the Google forums, I came across an issue with GDrive not loading in Firefox. https://support.google.com/drive/thread/1987396?hl=en&msgid=22679169
The last comment on the page the user mentions disabling CORS
Find a solution ! When the add-in CORS (Access-control-Allow-Origin)
is enabled impossible to load the google drive page but no problem
when it is deactivated.
Have you tried disabling the CORS? http://testingfreak.com/how-to-fix-cross-origin-request-security-cors-error-in-firefox-chrome-and-ie/
This will happen if you try to copy/paste info from a place that is restricted. Make sure editing is turned on for all users. If it’s not “shared” correctly it will glitch.

All div overflow:auto scrollbars are hidden in some Chrome browsers for ExtJS 5.1.0 apps

General Problem
We've had a long-standing problem with our two ExtJS 5.1.0 apps that div scrollbars don't show in Chrome, using only our QA testers' AWS Workspace Chrome browsers. They don't see this in other websites using that Chrome, only our two applications. We've been able to ignore this since the problem was isolated, but now a user is having the same problem.
We've been able to confirm that the difference is that wherever there's a div that should be overflow: auto is being generated as overflow: hidden. So scrollbars for grids, dropdowns, etc don't render but the div can still be scrolled via other means (tabbing, page down).
I've been looking for general ideas about what could cause this--is it ExtJS? Windows setting? Chrome setting? Again, the problem is isolated to AWS Workspace's Chrome and a user's Chrome.
Versions
Chrome:
AWS Workspace has exact same Chrome version as me, 79.0.3945.88.
User has Chrome 80.0.3987.149 (up-to-date).
Windows:
AWS Workspace is Windows Server 2016 Datacenter.
User has Windows 10.
What We've Tried
These are all troubleshooting steps we've tried in the AWS Workspace Chrome:
Disabled all extensions. Also ran in incognito mode which should do this also. The extensions are nothing that I don't also have, and I don't see the problem.
Inspected Chrome's flags--they're all default, and again not different than what I have.
Disabled Chrome's “Use hardware acceleration when available” setting and restarted Chrome.
Previously opened a ticket up with AWS and they were unable to help.
Researched any connection of this to Chrome, ExtJS, or Windows Server 2016 Datacenter without luck. Only found general information about "what to do if you have scrolling problems in Chrome".
Other Problems Our Apps Have in AWS Workspace Chrome
Listing these in case it helps trigger any ideas about the underlying problem, but focusing on the scrolling for now. Again these are isolated to Chrome in AWS Workspace (unclear if the user is seeing these also):
Drag and drop doesn't work.
Tabs that aren't the selected tab when the tab bar is loaded don't load at all.
It turns out that the problem was related to touchscreens. Our user has a touchscreen laptop (and didn't realize it for a while, we asked about this early on). And the Amazon Workspaces are touchscreen-compatible, as they have a "HID compliant touch screen" device listed in Device Manager > Human Interface Devices. So something about touchscreens + Chrome/Edge is telling ExtJS 5.1.0 that the device is mobile and scrollbars shouldn't be rendered.
Solutions:
For our user, she was happy to disable her touchscreen device and this worked for her.
For Amazon Workspaces, disabling the touchscreen device did not work. For Chrome we were able to resolve by adding --touch-events=enabled to the Chrome shortcut. There are various touch-related Chrome flags mentioned online as a solution, but none of those are available in the current version. Anything touch-related we did find in Chrome's list of flags didn't help.
I haven't looked for a solution for Edge if someone uses Edge and wants to keep their touchscreen. This is fine for us right now. (Because we realized Edge has the problem also, presumably due to Chromium. Did not see it with Firefox.)
And I did confirm using ExtJs' Kitchen Sink examples that I can replicate the problem in 5.1.0 with both a touchscreen laptop and an Amazon Workspace. Also that I can't replicate the problem in the current version, so we should be good once we upgrade.

Google maps API doesn't work in safari

hello im hosting Google maps API on my localhost for now, and it appears fine in Chrome and the mobile phone version. (both safari and chrome iPhone versions).
My problem is Google maps doesn't show when it comes to my Mac version of Safari. the Grey(background) shows and the cursors change to the Google maps cursor, but the map and content doesn't display. what can be the problem?
Here is a link to the map. as you can see the map displays in Chrome but not in safari.(at least not for me).
http://jsbin.com/cahicomame/1/edit?html,output
there is no guarantee that navigator.geolocation.getCurrentPosition will return a result. The user may deny the permission or the geolocation-service may not be able to locate the user.
You better initialize the map with a default-center (center is required to display the map).
I find the solution after 1 hours , it's because my website (developpement) was in http and not https :) Safari will ask your localisation.

Google MAP API does not work in https mode

I have integrated Google MAP api into our application using Javascript but unfortunately it does not work in https mode until I click "Show all content" button displays in the bottom of IE. There is no problem with http mode. Please let me know how can I fix it.
are you including the Google MAP script in a protocol agnostic way or just using an http link? if you want to server both, the script pointing to google maps should be
<script src="//maps.googleapis.com/maps/api/js?v=3.exp&sensor=false"></script>
so that either http or https is used.
If you check the 'Enable Protected Mode' box under Internet Options > Security > Local Intranet this seems to have the effect of allowing the map to display in IE 8 and 9 for users on a corporate network.
This of course seems counter-intuitive, especially given the explanation in this link
but it has solved the problem for my users on many occasions. Not ideal, but worth a shot if you can recreate the problem and see if this is the fix.