Why does AngularJS show me that a scope variable is undefined in directive when it is clearly defined? : I have an angularJS directive that I call like this:

    <rpt-closing closing-begin-ts="'None'" closing-begin-ts="'2014-11-25 23:59:59'"></rpt-closing>

Here is what the directive code looks like:

	  .directive('rptClosing',function(){
	      return {
	        restrict:'E',
	        scope: {
	          closingBeginTs: '=',
	          closingEndTs: '='
	        },
	        link: function(scope, element, attrs) {
	          console.log('*******************************************');
	          console.log('scope = ', scope);
	          console.log('scope.closingBeginTs = ', scope.closingBeginTs);
	          console.log('scope.closingEndTs = ', scope.closingEndTs);
	          console.log('*******************************************');
	        },
	        template: '<div>BLAH BLAH BLAH</div>'
	      };
	    }
	  )

This code works perfectly fine in [this jsFiddle][1]. I can see the values of `scope.closingBeginTs` and `scope.closingEndTs` in the console output. 

However, when I run the same codebase on my machine, it doesn't work! I can see that those two values are properly attached to the `scope`. But when I try to log them to the console, it shows `undefined`. Why? You can see what I mean in the screenshot below. Very weird indeed.

[![enter image description here][2]][2]


  [1]: https://jsfiddle.net/xgxwqxun/
  [2]: http://i.stack.imgur.com/aLkue.png