There is some confusion because you added the http://www.william-map.com/20100718/1/test.htm?0 test case after the bug had been marked "FixedNotReleased". With the subsequent release Luke updated the bug status to "Fixed".
We have also fixed http://www.william-map.com/20100718/1/test.htm?0, but that was a later change which is due for the next release. If you'd like, you can reopen the issue and we'll reverify your additional case at the next release. Cheers Ben On Thu, Jul 22, 2010 at 12:47 PM, William <[email protected]> wrote: > On Jul 20, 4:38 pm, Ben Appleton <[email protected]> wrote: >> >> I have just verified: >> http://www.william-map.com/20100718/1/test.htm?0 >> has been fixed internally. >> The fix should be released this week. >> > sorry Ben I don't quite understand what "fixed internally" means, when > the issue has been marked as Fixed in 3.1, and noted in the changelog > for 22/07/2010, but I still see a problem with this example? > > ... > > -- > 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. > > -- 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.
