Supported Browsers in V3

[Daniel Lee]

Hey everyone,

If you haven't read the blog post regarding supported browsers in V3,
take a moment and check it out:
http://googlegeodevelopers.blogspot.com/2010/03/supported-browser-updates-for-maps-api.html

The main points to note are the following:
- List of supported browsers for V2 and V3 were split and will soon be
reflected in the FAQ: http://code.google.com/apis/maps/faq.html#browsersupport
- List of supported browsers for V3 will be updated on a regular basis
- Removed support from the following browsers for V3: FF2, IE6,
Safari3
- Added support to the following browsers for V3: Chrome (Mac/Linux),
Android

The driving force behind our decision to decrease support for older
web browsers is because of our growing list of features which exploits
the potential of HTML5.

As always, if you have any questions or concerns, please reply back to
this thread.

Thanks!

Dann

[Sharath Dodda]

Hi Dann,

I have gone through the "Supported browser updates for Maps API v3"
documentation. My question is: what happens when users of IE6 access
the application which is using API v3? Most of our application user
base will be using IE6. So, we would like to know what happens for IE6
users.

Thanks for your response in advance.

regards,
Sharath.

> take a moment and check it out:http://googlegeodevelopers.blogspot.com/2010/03/supported-browser-upd...

>
> The main points to note are the following:
> - List of supported browsers for V2 and V3 were split and will soon be
> reflected in the FAQ:http://code.google.com/apis/maps/faq.html#browsersupport
> - List of supported browsers for V3 will be updated on a regular basis
> - Removed support from the following browsers for V3: FF2, IE6,
> Safari3
> - Added support to the following browsers for V3: Chrome (Mac/Linux),
> Android
>
> The driving force behind our decision to decrease support for older
> web browsers is because of our growing list of features which exploits
> the potential of HTML5.
>
> As always, if you have any questions or concerns, please reply back to
> this thread.
>
> Thanks!
>
> Dann

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[geoco...@gmail.com]

On Mar 26, 12:30 pm, Daniel Lee <daniel...@google.com> wrote:
> Hey everyone,
>
> If you haven't read the blog post regarding supported browsers in V3,

> take a moment and check it out:http://googlegeodevelopers.blogspot.com/2010/03/supported-browser-upd...

>
> The main points to note are the following:
> - List of supported browsers for V2 and V3 were split and will soon be
> reflected in the FAQ:http://code.google.com/apis/maps/faq.html#browsersupport
> - List of supported browsers for V3 will be updated on a regular basis
> - Removed support from the following browsers for V3: FF2, IE6,
> Safari3
> - Added support to the following browsers for V3: Chrome (Mac/Linux),
> Android
>
> The driving force behind our decision to decrease support for older
> web browsers is because of our growing list of features which exploits
> the potential of HTML5.
>
> As always, if you have any questions or concerns, please reply back to
> this thread.

The referenced post says:
+ The browsers that we no longer support for the Maps API v3 will
continue to be supported for the Google Maps
+ JavaScript API v2. We have no plans to change the list of supported
browsers for the Maps API v2, and
+ consequently if support for these browsers is important to you we
recommend that you continue to develop your + applications using the
Maps API v2.

But API v2 is now been deprecated. This seems to make the decision
for developers difficult. New feature development will be in v3, but
not all browsers will be supported. Some people are stuck with
ancient browsers in the corporate environment, therefore to support
the widest audience, you need to use v2...

-- Larry

[Sharath Dodda]

Hi there,
Thanks for your response. We are not interested in new features of V3.
We are happy with what V2 offers, as there is an existing application
developed using V2. Having said that, we would like to know what are
the bottlenecks around taking up new development using V2.

Based on this, we need to make some decisions. Your quick response is
appreciated.

thanks again,
Sharath.

On May 24, 9:06 pm, "geocode...@gmail.com" <geocode...@gmail.com>
wrote:

> On Mar 26, 12:30 pm, Daniel Lee <daniel...@google.com> wrote:
>
>
>
> > Hey everyone,
>
> > If you haven't read the blog post regardingsupportedbrowsersinV3,
> > take a moment and check it out:http://googlegeodevelopers.blogspot.com/2010/03/supported-browser-upd...
>
> > The main points to note are the following:

> > - List ofsupportedbrowsersfor V2 andV3were split and will soon be

> > reflected in the FAQ:http://code.google.com/apis/maps/faq.html#browsersupport

> > - List ofsupportedbrowsersforV3will be updated on a regular basis
> > - Removed support from the followingbrowsersforV3: FF2, IE6,
> > Safari3
> > - Added support to the followingbrowsersforV3: Chrome (Mac/Linux),

> > Android
>
> > The driving force behind our decision to decrease support for older

> > webbrowsersis because of our growing list of features which exploits

> > the potential of HTML5.
>
> > As always, if you have any questions or concerns, please reply back to
> > this thread.
>
> The referenced post says:

> + Thebrowsersthat we no longer support for the Maps APIv3will
> continue to besupportedfor the Google Maps
> + JavaScript API v2. We have no plans to change the list ofsupportedbrowsersfor the Maps API v2, and
> + consequently if support for thesebrowsersis important to you we

> recommend that you continue to develop your + applications using the
> Maps API v2.
>
> But API v2 is now been deprecated.  This seems to make the decision
> for developers difficult.  New feature development will be inv3, but

> not allbrowserswill besupported.  Some people are stuck with
> ancientbrowsersin the corporate environment, therefore to support

> the widest audience, you need to use v2...
>
>   -- Larry
>
>
>
> > Thanks!
>
> > Dann
>
> --

> You received this message because you are subscribed to the Google Groups "Google Maps JavaScript APIv3" group.

[Sharath Dodda]

Hi there,
Thanks for your reply. We don't require new features of V3. We are
fine with V2 features (as already there is an existing application on
V2 and we are happy with that). Having said that, will there be any
disadvantages if we develope the new applications using V2?

Thanks again for your reply, in advance.
Sharath.

On May 24, 9:06 pm, "geocode...@gmail.com" <geocode...@gmail.com>
wrote:

> On Mar 26, 12:30 pm, Daniel Lee <daniel...@google.com> wrote:
>
>
>
> > Hey everyone,
>
> > If you haven't read the blog post regardingsupportedbrowsersinV3,
> > take a moment and check it out:http://googlegeodevelopers.blogspot.com/2010/03/supported-browser-upd...
>
> > The main points to note are the following:

> > - List ofsupportedbrowsersfor V2 andV3were split and will soon be

> > reflected in the FAQ:http://code.google.com/apis/maps/faq.html#browsersupport

> > - List ofsupportedbrowsersforV3will be updated on a regular basis
> > - Removed support from the followingbrowsersforV3: FF2, IE6,
> > Safari3
> > - Added support to the followingbrowsersforV3: Chrome (Mac/Linux),

> > Android
>
> > The driving force behind our decision to decrease support for older

> > webbrowsersis because of our growing list of features which exploits

> > the potential of HTML5.
>
> > As always, if you have any questions or concerns, please reply back to
> > this thread.
>
> The referenced post says:

> + Thebrowsersthat we no longer support for the Maps APIv3will
> continue to besupportedfor the Google Maps
> + JavaScript API v2. We have no plans to change the list ofsupportedbrowsersfor the Maps API v2, and
> + consequently if support for thesebrowsersis important to you we

> recommend that you continue to develop your + applications using the
> Maps API v2.
>
> But API v2 is now been deprecated.  This seems to make the decision

> for developers difficult.  New feature development will be inv3, but

> not allbrowserswill besupported.  Some people are stuck with
> ancientbrowsersin the corporate environment, therefore to support

> the widest audience, you need to use v2...
>
>   -- Larry
>
>
>
> > Thanks!
>
> > Dann
>
> --

> You received this message because you are subscribed to the Google Groups "Google Maps JavaScript APIv3" group.

[Daniels Lee™]

Hey Sharath,

You can continue developing on V2.  However, it is a deprecated API, meaning no new features are being introduced, and you will have to migrate at some point.  V3 offers significant performance benefits which would improve latency and user experience in your app.  Migrating sooner rather than later also saves on implementation time in the future.  If no further development is being done on your app however, I understand the reasons to stick with V2 for the time being.

Regarding the question around V3's lack of official support for IE6, it does pose an interesting concern.  We do try to take IE6 bugs into consideration, but supported browsers do take priority over these demands.

If you find certain V3 features not working in IE6, please report them to us in the issue tracker so we're aware of them.

http://code.google.com/p/gmaps-api-issues/

Thanks!

Dann

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.

To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

--
Daniels Lee
Developer Programs Engineer
Google, Inc.
345 Spear Street
San Francisco, CA 94105
650 253 0967