Just wondering if anyone else is encountering this error when zooming in\out (either with mouse wheel or arrows) on the newly released API for JS 3.9? See below: [ATTACH=CONFIG]32915[/ATTACH]
Functionality does not seem to be impacted...I've tried both the 3.9/ and 3.9compact/ distros and they both throw errors.
Unfortunately we didn't notice this in time to fix it. There are no side effects, and it doesn't block any actual errors. The underlying reason this happened is that with version 3.9, we made dojoConfig.useDeferredInstrumentation true so that errors that happen during the lifecycle of a deferred are reported (since so much of the API is async, this makes a big difference in the errors the API reports and should make debugging while you're building something easier).
So why does this happen during map navigation, specifically rapid zoom events? Since map navigation methods return deferreds, doing more than one rapidly cancels all but the last deferred. So when you scroll your mouse wheel a lot, or click the + or ??? on the map multiple times, multiple deferreds are created and all but the last one is canceled. Because useDeferredInstrumentation is set to true, you see the error you mentioned. We will hopefully get this fixed for 3.10. Until then, please ignore these errors.
Edit: If you want this to go away, put useDeferredInstrumentation: false in your dojoConfig, but you'll be losing the benefits of better error reporting.
Unfortunately we didn't notice this in time to fix it. There are no side effects, and it doesn't block any actual errors. The underlying reason this happened is that with version 3.9, we made dojoConfig.useDeferredInstrumentation true so that errors that happen during the lifecycle of a deferred are reported (since so much of the API is async, this makes a big difference in the errors the API reports and should make debugging while you're building something easier).
So why does this happen during map navigation, specifically rapid zoom events? Since map navigation methods return deferreds, doing more than one rapidly cancels all but the last deferred. So when you scroll your mouse wheel a lot, or click the + or ??? on the map multiple times, multiple deferreds are created and all but the last one is canceled. Because useDeferredInstrumentation is set to true, you see the error you mentioned. We will hopefully get this fixed for 3.10. Until then, please ignore these errors.
Edit: If you want this to go away, put useDeferredInstrumentation: false in your dojoConfig, but you'll be losing the benefits of better error reporting.
