I am puzzled by Google's decision not to support Opera also.  Opera supports both 
CANVAS and SVG with one exception.  The "globalCompositeOperation" is broken in 
Opera.  Perhaps Google could persuade Opera to fix it.

I have several demos running just fine in Opera:

    http://www.polyarc.us/polycluster

Click "Experimental".  Click "Examine" to see the entire DOM structure.  Click "Use 
SVG" to toggle between CANVAS and SVG on the fly.  Click the "View" tabs to toggle 
between different views.

Opera support is still limited, but I've filed this internally.

(No comment was entered for this change.)

(No comment was entered for this change.)

This issue is marked as fixed, but I have been unable to get any of the examples to
work in Opera. Tested with Opera 10.10 on Windows 7.

https://code.google.com/intl/ru/apis/maps/documentation/v3/examples/polygon-simple.html

I can confirm chadkill's findings. This is still not working in Opera 10.10 nor 
10.50 beta (Mac). Can this be reopened?

I can unfortunately confirm the polygons not working in Opera 10.10 nor 10.50 (both 
on Win 7, x64), neither in the last Opera of the 9.x line (I can't recall the exact 
version number) on Win XP, x86.

Latest version of opera on WinXP 32bits. Still broken.

Solve it please?

Not working in Opera 10.51 in Win7 x64 either.

Can this bug be reopened? It is not working on Opera 10.53/Mac.

Also not working on Opera 10.53/Win.

To be more precise, it would seem that the fillColor is not honored.  If I give the 
polygon some border, then the border *will* render.  However, the border will not 
render in the color specified, NOR is the polygon managed properly:  as you zoom in 
and out, more and more polygons are rendered.  Reason for this appears to be that the 
removeOverlay function fails to delete the polygon.  It doesn't work for me, and nor 
does it appear to work for the Google Maps API...

I've confirmed and reopened the bug with the team.

Thanks for verifying.

Polylines are also not rendering in Opera 10.5 (Opera/9.80 (Windows NT 6.0; U; en) Presto/2.5.24 Version/10.53)
E.g: https://code.google.com/apis/maps/documentation/javascript/examples/polyline-simple.html

Polylines are not rendering in Opera 10.6 on Windows with current v3 API. For example:

https://code.google.com/apis/maps/documentation/javascript/examples/polyline-simple.html

Neither working in Opera 10.60 on Kubuntu 10.04 x86_64

Opera is not currently a supported browser for the Maps API. Supporting a browser is not just a policy decision. To support a browser we must add it to our automated test suite, and then ensure it passes all tests now and ongoing. So there is an overhead associated with supporting additional browsers. We have to balance that overhead against the volume of requests we see from that browser and decide if the adoption amongst users merits the cost.

We can not support Opera Mini, because it does not have a sufficient level of JavaScript support. This leaves Opera for Desktop and Opera Mobile. Together these two browsers account for less than 1% of the requests we receive for the Maps API v3. Perhaps the strongest argument for supporting Opera is that it would open up the API to a number of new platforms (eg. Symbian, WinMo). However when we exclude requests from platforms for which we already have a supported browser, that number drops to 0.05%. So right now supporting Opera is simply not a good investment of our engineering time compared to working on features that will benefit 100% of the developer and user base.

Consequently I am going to collapse all bugs relating to Opera into this one, and reclassify this as a Feature Request to support Opera. We will continue to keep an eye on this issue and on the adoption numbers, and if a new strong argument arises, or adoption increases, we will revisit it.

 Issue 2213  has been merged into this issue.

 Issue 2438  has been merged into this issue.

(No comment was entered for this change.)

On my site, with about 20 000 visits daily according to Google Analytics, 5% of the visits have been done using Opera during the past month. I admit that my sample is very small and the user base is biased to some slightly technical direction, but could you please check your statistics for the requests that you receive for Maps API v2? Could it be that the amount of Opera requests is small on v3 because some things are not quite working?

I don't use Opera myself, but some users are a little bit annoyed.

As web developer myself, I would like to make a small comment on these statistics and the Opera polygons:
(1) I never develop for IE - of all the browsers out there, it is simply the most dismal in terms of performance and standard compliance, certainly before V8 (which I have not tested much).  I develop my code for Opera (very good standard-adherence), debug in FF (old habits, and all that) and test in Chrome.  Only when that all works will I tackle IE (and usually end up tearing my hairs out).
(2) IE's market share is driven by monopolistic bundling and an unthinking customer base.  Do not compare other browsers against IE.  Simply remove IE from all statistics and ask yourself: what is the market share of the other browsers?  I think this is the only relevant number, and Opera's share will seem a lot more significant.  It doesn't mean we can ignore IE (sadly).  We just have to accept that whatever we do has to work - somehow - under IE.
(3) Maps polygons work in all browsers except Opera.  If I were Google, I'd log a bug report with Opera and see what transpires.  If Opera can make the case that their browser is doing the right thing, then any number of other browser implementations are wrong.  If that's the case, Google's code becomes unsafe as any of these working browsers may cease to work at any point.  It should be changed.  Alternatively, Opera need to revisit their engine.

I worked on it for a while and I think that I can propose quite reasonable solution. As we all know Opera is always very precise when it comes to implementing web standards and inline SVG is part of XHTML standard, which AFAIK should be served with 'application/xhtml+xml' content type.

If a well formed XHTML file is served as text/html Opera doesn't render SVG (which I personally think is quite reasonable). Here are two examples, in which I'm using inline svg taken from "polyline simple" example (in v3).

These are exactly the same documents apart from content-type header,
first one served as text/html:
http://michaljankowski.pl/svg/text_html.html

second one served as application/xhtml+xml:
http://michaljankowski.pl/svg/application_xhtml.html

So because in Google Maps SVG elements are correctly added to DOM in Opera, and the problem is that they're not rendered I assume that this may be the main (if not the only) problem.

I can imagine that adapting Google Maps for various browsers must by a tremendous work to do but maybe you could just check this out. If this works you could make a lot of developers and 1% of you users a bit happier (and I think that 1% of your users is a huge number of people).

Hello,

I'm agree with previous comments. Opera is a web standard compliant web browser, it should not be a so big problem for the map API V3 to support it.

Beware of that the API users may begin to think that the true reason is concerning the web browser competition, Opera is a great rival on mobile....

Cheers

Opera 10.70/3452, Windows 7 x64, all polylines and polygons (at least those I checked) finally working! I'm just wondering if it's Google's or Opera's doing.

Indeed polylines works for me in 10.60 too !!!
thanks to google!!

Working for me as well on Kubuntu 10.04 / Opera 10.60. Thanks google!

Works great (tested on Opera 10.10, 10.60, 10.70). Cheers!

(No comment was entered for this change.)

Opera 10.60 on Windows 7 works correctly. Good job, tkanks.

So can you reopen    Issue 2438  , please?

I'm happy to hear that some of the issues that previously affected the Opera browser have been resolved. However this is not a reflection of a change in our position on Opera support.

Opera and Google Maps seems to work pretty well for all intents and purposes, even though they lack official support. The main reason behind this is that Opera tries hard to follow the web standards, which means that google Maps almost never has to do anything special to make it work in Opera.

Naturally, it follows that as long as the Google Maps API does not suddenly add any "if(opera) stopMap();"-code - Opera will continue to work with Google Maps also in the future. 

According to our changelog this was fixed on Jul 22:
https://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIv3Changelog