I've been receiving disturbing warning messages in the Chrome dev tools console window while working on a WAB dev edition version 1.2 application. I think I'd seen (and ignored) the messages earlier, but I believe the warning about features that "will be removed" in April 2016 is a recent addition to the warning message.
Here is the first message:
The XMLHttpRequest progress event property 'position' is deprecated and will be removed in M50, around April 2016. Please use 'loaded' instead. See https://www.chromestatus.com/features/5044837464145920 for more details.
and the second message:
'KeyboardEvent.keyLocation' is deprecated and will be removed in M50, around April 2016. Please use 'KeyboardEvent.location' instead. See https://www.chromestatus.com/features/4997403308457984 for more details.
Both messages show up referring to "dojo.js" lines.
Am I right to to be very afraid of these warnings? Will applications built on Dojo and Esri (WAB 1.2 / JSAPI 3.14) cease to work with Chrome browsers when the version 50 update occurs (latest version of Chrome is currently 49.0.2623.110 m)? What are my options to prevent that from happening?
Does the latest version of the JSAPI (version 3.16) resolve this issue?
It seems from some poking around that these are core Dojo issues: http://stackoverflow.com/questions/27175603/the-xmlhttprequest-progress-event-property-position-is-d...
Any insights into this situation are greatly appreciated!
I did some looking and you can download the chrome 50 beta from Chrome Release Channels - The Chromium Projects
they mention that you should back up all your user settings bookmarks, plugins etc since you can not run both the beta and current version on your computer at the same time.
I am going to give it a shot on a test computer and see how it goes. i will update here.
O n chrome beta 50 I tested my 1.2 developer edition application which has moderate customization and on first glance everything seems to be working fine. I also had no warning messages in the console regarding the deprecation of the XMLHttpRequest position property.
Still this is not very conclusive so it would be nice if someone else with more knowledge could chime in?
I'm assuming that you also have seen the deprecation warning messages in Chrome release version 49 (dev tools console)?
So are you saying that the deprecation messages don't show up in Chrome Beta 50 (dev tools console)?
Thanks for running the test with the Beta version!
Hi, yes i should have mentioned. When first loading the application I also see the deprecation warning message (The XMLHttpRequest progress event property 'position' is deprecated and will be removed in M50, around April 2016. Please use 'loaded' instead....)
I have not however seen the KeyboardEvent.keyLocation. do you see that one on load or at another time?
No problem for testing, im concerned too!