[regression]dojo.parser needs explicit dojo.require in 1.7

[Douglas Hays]

In dojo 1.6, you could specify parseOnLoad:true in djConfig and the dojo.parser would automatically be run even if you did not do a dojo.require('dojo.parser') in the web page's HEAD section. Starting with Dojo 1.7, you have to add the dojo.require. Since this will affect backward compatibility, I wanted to make sure this was intentional before we ship 1.7.

[Chris Mitchell]

marking mustfix 1.7

[bill]

This is expected behavior, although the characterization in this ticket is a little off. From the ​1.7 release notes (migration section):

• You may need to explicitly require the following modules which were getting implicitly loaded before:
  • dojo.parser (many widgets which used to include the parser no longer do)

In other words, dojo.require('dojo.parser') was required since 1.0, but you just got away with it until now.

[bill]

Note that this change is unrelated to the AMD work, it's just part of our code refactor to streamline for mobile.

[Chris Mitchell]

there is a very large # of customers that will be broken if this is the new behavior. If there is technically a way to keep this working with the same behavior as 1.6, we should through the 1.x stream, and note deprecation in debug log.

[bill]

Sorry, but this is the direction we are going for 1.7, to allow lightweight applications (especially mobile). See #12432 for details, and note that any of the changes associated with that ticket will cause similar problems.

[Douglas Hays]

For the record, adding "dojo/parser" to the define for _Widget.js would prevent almost all backward compat issues and doesn't seem to affect mobile at all.

[Chris Mitchell]

why are we not considering the fix doug recommends for 1.x? This will result in many customer defects coming in.

[bill]

As explained in #12275, the goal is lightweight templated widgets. It's not strictly for mobile, but it affects any mobile application using widgets from dijit.

And again, this is not a regression, it's operating according to the original spec from 1.0.

Stop reopening this ticket.

[bill]

Note: original documentation is at ​http://docs.dojocampus.org/dojo/parser?action=recall&rev=2

[Douglas Hays]

How about appending this to the end of _Widget.js (or any other JS file) in order to throw a deprecated warning:

if(dojo.config.parseOnLoad && !dojo.isAsync && !dojo.parser){
        dojo.ready(99, function(){
                if(!dojo.parser){
                        dojo.deprecated("Add explicit dojo.require('dojo.parser');", "", "2.0");
                        dojo.require("dojo.parser");
                }
        });
}

[bill]

Adding that code to _TemplatedMixin would fix the "regression" in dijit. Adding it to _WidgetBase would fix the "regression" in dojox.charting (since the charting widgets were changed to not use templates, thus no longer pulling in the parser), albeit breaking dojox.mobile apps which already load an alternate parser.

But, if users expect the parseOnLoad flag to automatically load the parser, it should really happen regardless of whether anything in dijit is loaded or not. (Remember that parser is part of dojo core, not part of dijit.) So, last time I talked to Rawld he thought that made sense, to put the code to load the parser into the kernel.

[Rawld Gill]

(In [25467]) moved dojo.ready calls in base to dojo/ready module; added feature to load parser as per #12907; fixes #12907; refs #13113

[bill]

(In [25522]) remove unneeded parseOnLoad: true from robot test files, refs #12907