Google Maps v3 kml polygon transparency in IE8 - google-maps

Starting some time around March 13th, I started receiving bug reports from
users that my KML polygons were no longer transparent on Windows XP, and IE8.
I did notice Windows XP updates were applied before issues were first reported to me.
The transparency works fine on any other OS/Browser I have available to test.
(Windows XP with Chrome and Firefox, IE11 on Windows 7, Firefox and Chromium on Ubuntu 10)
Nothing has changed in my generation of the map, or the KML it uses.
I've been able to recreate this with a very simple test:
http://itic.occinc.com/googleMapTest.html
It uses this KML:
http://itic.occinc.com/test.kml
I've tried using different colors in the KML with more and less opacity/transparency.
For now I've disabled the polygon filling in my applications, but I'd like to re-enable that.
Any suggestions are appreciated.

This bug was reported at https://code.google.com/p/gmaps-api-issues/issues/detail?id=6540 and should be resolved

Related

Mac M1 Processor + Chrome Browser v105 = Inconsistent HTML5 Canvas Element

TL;DR Canvas Elements not showing up for some sites and does show for others. How can I have it show consistently?
I have a 2021 Macbook Pro with an Apple M1 Pro processor. I use Chrome Browser v105.0. On some sites that use the HTML5 canvas element, I am able to see stuff being drawn on the canvas but for other sites, the canvas element is clearly there but nothing is drawn on it. I tried playing with the chrome://flags that have to do with GPU and Canvas by switching them on and off to see if I can get Canvas Elements showing up consistently and now they do show for the sites that it was not working for but only after refreshing the page.
Has any one experienced this before and if so, is there a way that I can have canvas elements show consistently without all the workaround?
I am experiencing the same issue with HTML5 canvas on Chrome M1, seems to be related to Apple Silicon (M1) + Chrome 105 because it's working fine on Chrome v105, on a Windows/MacOs Intel computer. It is fixable (on your client only) by disabling the 'Out-of-process 2D canvas rasterization' flag on chrome://flags. Still waiting Google to fix this issue as it is a breaking issue.
Edit : tested on Chrome Beta (v106.0.5249.30) and the issue is still present
We experience the same problem (only with the Apple M1 processor, Apple M2 not tested). We developed an app using the canvas element. It worked fine with Apple M1 and Chrome (till v104). When Chrome v105 was launched the problem started and the canvas element didn't draw anything anymore. The problem only occurs when the flag accelerated 2d canvas is enabled. When this flag is disabled the canvas works fine again. This is a breaking issue and should be fixed by Google. Everything works fine in the latest version of Safari and Firefox with acceleration enabled.
The problem is fixed with Google Chrome v107. Topic can close.

ui-leaflet Heat Plugin conflicts with ui-leaflet-draw for microsoft browsers

I have an AngularJS (1.58) webapp showing some maps with ui-leaflet.
I have integrated the Leaflet.Heat Plugin, successfully. Also, I have integrated the Leaflet.Draw Plugin successfully.
Problem:
The moment Im using both Plugin, Heat and Draw, my webapp is not showing any maps anymore on microsoft browsers (Microsoft Edge, Internet Explorer 11). I have tried to use different combinations of release versions of these plugins to get it to work on every of the common browers. When I bring the leaflet maps back to working on Microsoft Edge, the Heat Plugin is not anymore working (not only ME, also not Opera, Firefox, GChrome).
Summed up:
The latest versions of ui-leaflet, Leaflet, ui-leaflet-draw and Leaflet.Heat
are working fine together on Google Chrome, Firefox, Opera. But the maps are totally disappearing for Microsoft Edge. Older versions are showing maps again for Microsoft Edge, but the Heat Plugin is not anymore working on any browser.
Question: Is there a working combination of versions of these tools for all these browsers (speaking of Google Chrome, Firefox, Opera, Microsoft Edge) together? If so, which versions are them? If not, are there recommended workarounds? Maybe other plugins, which I can use instead for drawing or showing well-looking heatmaps?
Steps to reproduce:
Download the Leaflet.Heat example. Integrate ui-leaflet-draw as Librarys (e.g. via bower).
Test it with Google Chrome, Firefox, or Opera. Depending on your versions, you gonna either see the working Heatmap but tested with Microsoft Edge you dont see any map OR you dont see any heatmap, and microsoft edge shows u a map (also without heat).
Alright, I was focusing my issue and find a solution.
I replaced ui-leaflet-draw with leaflet.Draw plugin and the combination of all 3 worked for all browsers (as long as I am using the correct versions).
So here they are from my bower.json project file:
"dependencies": {
"angular": "1.5.8",
"angular-simple-logger": "~0.1.7",
"ui-leaflet": "1.0.3",
"Leaflet.heat": "https://github.com/Leaflet/Leaflet.heat/archive/gh-pages.tar.gz",
"angular-material": "~1.1.1",
"leaflet.draw": "*"
},
"resolutions": {
"angular-material": "~1.1.1",
"angular": "1.5.8",
"leaflet": "1.0.3"
}
Update: Leaflet 1.0.3 working too and has better user expierence controls then 0.7.x
Enjoy developing nice maps with Heat layers and Draw controls now working for GChrome, Opera, FireFox, and Microsoft Edge! (havent tested IE 11 cuz of lots of other conflicts with angular-material)

Can't zoom or navigate Google Maps on Windows phone

I have a Windows Phone (a Nokia Lumia) from which I recently encountered an issue. I can't zoom (pinch zoom) or navigate (scrolling with the finger) using Google Maps. It was possible I believe last week or the week before that, but now it's not working anymore.
I can't recall any updates issued in between last working date and now, nor have I fiddled with any options.
I saw in a thread that one could use the options in the browser in order to enable zooming. But this option is not present for me. I use Internet Explorer.
Based from this thread, if it was determined that you are on a desktop version or IE, it will allow zooming to be controlled by mouse. Touch won't work at all. I also found this blog which states that:
The mobile Web version of Google Maps is optimized for WebKit browsers such as Chrome and Safari. However, since Internet Explorer is not a WebKit browser, Windows Phone devices are not able to access Google Maps for the mobile Web.
The desktop version of Google Maps works just fine in these browsers. It's one thing for Google to say the mobile site isn't tested or supported in the mobile browsers, but the desktop version, at least, shouldn't be off-limits. The desktop version may not be ideal in a mobile browser, but it does work.

Google Chrome on 1440p Monitor on Windows 7

I basically tried everything and searched everywhere, but I can't make google chrome "scale" at the res of 1440p. All the things (Websites as well as UI) are way to small to read and use comfortably. I tried to edit the registry, enable chrome flags that are apparently not available anymore and modify the shortcut start parameters. What am I doing wrong?
(Windows is scaled to a 125%)
(Firefox, Opera and IE scale perfectly btw)

Is text API in HTML5 canvas still so slow?

I have read some articles about text API in canvas being slow in browsers. These articles are a year old, was there some improvement over this time? Does for example Google use canvas Text API in its Google Maps MapsGL?
I profiled this on my site recently using fillText() and strokeText():
fillText()
157.1ms Safari 5.1.7
215.8ms Chrome v21
210.6ms Chrome v22
426.1ms IE 9 (64bit)
994.5ms FireFox 15.0.1 994.
strokeText()
196.6ms Chrome v21
193.0ms Chrome v22
3793.1ms IE 9 (64bit)
6149.0ms FireFox 15.0.1
9628.8ms Safari 5.1.7
Yes, I think slow but really browser dependent. Test test code there and you can run it yourself but actually, FF may time out waiting for test to complete.
Looking at Google Maps GL, one can see that it uses a file called https://maps.gstatic.com/cat_js/intl/en_ALL/mapfiles/435c/maps2/%7Bmain,mod_util,mod_vt%7D.js
In that, there are indeed calls to fillText(), there are 6 instances of "fillText" in the file.