Bing Maps faulting in FF and Chrome since yesterday evening RRS feed

  • Question

  • In FF as soon as the initialize starts we get the message 'l is not a function' (in firebug) residing in veapidelay.js / initMapDelayCode.

    Chrome gives a error as soon as interaction starts: 'Uncaught Error: DISPATCH_REQUEST_ERR: DOM Events Exception 1'.

    We were able to reproduce both the bugs with the example code from the MSDN site: http://msdn.microsoft.com/en-us/library/gg427609.aspx (example at the bottom).

    The bug in FF is causing random failing behavior (as in, no entities are being rendered on the map). So we would like to see this fixed soon.

    • Edited by RazrNL Wednesday, September 21, 2011 2:52 PM
    Wednesday, September 21, 2011 2:52 PM


All replies

  • This is a known issue that is being investigated. See this post: http://social.msdn.microsoft.com/Forums/en-US/vemapcontroldev/thread/c832cbd5-660c-48b7-b479-e4a954c49daf
    Wednesday, September 21, 2011 3:28 PM
  • FYI - FF issue is resolved. For Chrome, issue is known & is there for a while. It does not interfares with any map functionality. Said that, it is under our traction & would be fixed in coming release.

    Thanks for using Bing mapcontrol & reporting the issues.



    Hemant Goyal
    Wednesday, September 21, 2011 8:54 PM
  • Any status updates on the incompatibility with Bing Maps AJAX 6.3 and Chrome? Throwing an error on every 'mouseup' and 'mousedown' causes issues for people using 'window.onerror' to track errors in the browser.
    • Edited by Ryan Olds Friday, October 7, 2011 6:29 PM
    Friday, October 7, 2011 6:29 PM
  • This should be fixed now! Microsoft.Maps.Map.getVersion() should return 7.0.2011100111334.47 or try clearing cache.

    Hemant Goyal
    Friday, October 7, 2011 6:33 PM
  • I'm not using 7.0. I'm using 6.3.
    Friday, October 7, 2011 9:02 PM
  • There has been no updates to v6.3 for quick some time now, so this should not be new. if possible, recommed to move to v7, as all energy is directed on it.
    Hemant Goyal
    Friday, October 7, 2011 9:25 PM
  • This issue cropped up in 6.3 about the same time it cropped up in 7. We have plans to migrate to 7. However, like MSFT, we are very busy and will be following our own time table as to when we will be adopting new technology. In the mean time, we would appreciate it if this issue was fixed. We have been consuming error events using 'window.onerror' and sending them to a remote logging server and I assure you this issue cropped up recently (late/mid September). As far as I'm aware, 6.3 hasn't been discontinued and I have not seen any official EOL announcement regarding it.

    • Edited by Ryan Olds Friday, October 7, 2011 9:42 PM
    Friday, October 7, 2011 9:38 PM
  • As mentioned before there have been no updates to v6.3. Can you provide more information around the error you are getting? As for EOL there is no EOL planned for v6.3 at this time. Majority of Bing Maps users are still on v6.3 so I don't expect this version to be phased out for a while.
    Saturday, October 8, 2011 9:13 AM
  • The error is reproducabe with this code: https://gist.github.com/1275783, which is just a very slightly modified version of the example found at http://msdn.microsoft.com/en-us/library/ee692181.aspx (also has the error).

    The error happens on Chrome 14.0.835.202 m. Load the example, click on the map, then look at the web inspectors console. Every mousedown emits an error. Dragging emits and error on mousedown and mouseup.

    The error also happens at http://www.bing.com/maps/, which appears to be running a modified version of 7 that doesn't give a version using Microsoft.Maps.Map.getVersion().

    What other information do you need?

    Monday, October 10, 2011 5:01 PM
  • I've tried the code you provided and am unable to reproduce the issue you are reffering too. Both FF and Chrome work fine with the code you provided.
    Friday, November 18, 2011 5:17 PM