[regression] dojo.deprecated and dojo.experimental are no longer suppressed when isDebug=false

[Kenneth G. Franqueiro]

This is a behavioral regression from 1.6, but I'm not sure if it's intentional.

In Dojo 1.6 and lower, dojo.deprecated and dojo.experimental calls would only cause console messages if dojoConfig.isDebug is set to true before dojo is loaded.

In trunk, calls to dojo.deprecated and dojo.experimental always output to console. Rather than consulting isDebug, it appears to hinge on the has feature dojo-debug-messages, which is unconditionally set truthy in kernel.js. Perhaps this has test should consult the value of the isDebug config flag (if possible)?

[Adam Peller]

Not sure what to say about the change in behavior as it might relate to a "compatibility" promise, but I think there's good reason to at least have these warnings on by default, especially with us pushing towards 2.0.

[Rawld Gill]

In [26614]:

always define dojo.deprecated,experimental; give real defs based on has feature dojo-debug-messages or config.isDebug; thanks kgf; fixes #13939; !strict