There is a breaking change in angular v1.3.0-beta.15, so that, by default, angular will no longer look for controllers on window. See 3f2232b5 for more details.
With the exception of simple demos, it is not helpful to use globals
for controller constructors. This adds a new method to `$controllerProvider`
to re-enable the old behavior, but disables this feature by default.
BREAKING CHANGE:
`$controller` will no longer look for controllers on `window`.
The old behavior of looking on `window` for controllers was originally intended
for use in examples, demos, and toy apps. We found that allowing global controller
functions encouraged poor practices, so we resolved to disable this behavior by
default.
To migrate, register your controllers with modules rather than exposing them
as globals:
Therefore, to make your example work without creating your own module (not recommend though), you could add this code in the script tag at the bottom:
angular.module('ng').config(function ($controllerProvider) {
$controllerProvider.allowGlobals();
});
For a working example, see a plunker below.
Example plunker: http://plnkr.co/edit/xdlfJRpH8lHzNvqyQ0no?p=preview
与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
