The only solution I know of is testing: Test in as many different browsers as possible so that you're able to evaluate the annoyance and notice known failures (and their reasons) in a help/support page.
On Jul 25, 9:17 pm, Joseph Elfelt <[email protected]> wrote: > Kesuke, > > Thanks for your comments - not a hijack at all. > > There's obviously a larger and important issue, namely the pros and > cons of using browser detect code in v3 apps. > > If an app does not have browser detect code, then is there some way to > detect when a v3 app is giving the user a bad experience? > After all, if my app does not seem to be working right for someone > (due to their browser choice) I don't want them to be mad at the app > and I don't want them to be mad at me. -- 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.
