Could the old browser issue (IE6 at least) be circumvented altogether by that project I heard about which acts essentially as an ActiveX plugin which simulates a Google Chrome Browser that takes up the whole page, then renders the original page in itself? That seemed like a really clever solution for the archaic old browser issue.
And thanks for letting us know. On Mar 19, 3:11 am, "Thor (Google Employee)" <[email protected]> wrote: > Exactly. :-) > > And to tell you that if we can not make a new feature work on these > browsers, that will not stop us from launching it. > > On Mar 19, 2:09 pm, Josh Rosenthal <[email protected]> wrote: > > > > > So... the announcement is more a matter of giving us notice that if ya'll > > encounter a feature where the only way to implement it is break the old > > browsers, that won't stop you from implementing said feature, rather than > > telling us that you're not going to be paying any attention to whether or > > not you might break functionality on the old browsers. Sounds reasonable. > > > Thanks! > > Josh > > > On Thu, Mar 18, 2010 at 10:34 PM, Thor (Google Employee) < > > > [email protected]> wrote: > > > On Mar 19, 12:41 pm, Josh Rosenthal <[email protected]> wrote: > > > > > Is the intent that already > > > > existing functionality should remain functional? ie: Given a map I've > > > > already built in v3 of the API, which I don't plan to add features to, > > > and > > > > don't do anything to take advantage of new functionalities. Will my map > > > > continue to function under IE6, or will code be pushed that breaks > > > existing > > > > functionality in older browsers? > > > > Where possible we will maintain backwards compatibility for these > > > browsers. Only if a new feature is launched that requires changes > > > which can not be implemented in a way that avoids regressions on > > > unsupported browsers without significant negative impact on supported > > > browsers would be consider breaking backwards compatibility with > > > unsupported browsers. > > > > If this becomes necessary we will provide reasonable notice. There is > > > currently nothing on the roadmap that could require this, and I > > > suspect that by the time something like that comes along the usage of > > > these browsers will have declined so much as to make it > > > inconsequential. > > > > Many thanks, > > > > Thor. > > > > -- > > > 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 > > > [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<google-maps-js-api-v3%2B > > > [email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
