bug(autocomplete): ng-click doesn't work inside md-not-found

[stewones]

[snarayanank2]

+1 I'm running into this as well with version 0.11.4.

         <md-not-found>
            "{{searchCategoryTxt}}" not found.
            <a ng-href="#" ng-click="newCategory(searchCategoryTxt)">Add!</a>
          </md-not-found>

My controller function never gets called. As @stewones mentions, even the demo one doesn't work - it doesn't show the alert.

[makkart]

+1 has been working in RC-1 and maybe RC-2, not working in RC-3

[dominicgoulet]

+1 not working since RC1 for me.

[nextor2k]

as workout: self.$mdAutocompleteCtrl.mouseUp = function(){
$timeout(function(){ inputElement.focus(); });
};

its not good, but for those who need make it to work at any cost!

[dominicgoulet]

My current fix is the following:

<md-autocomplete md-search-text-change="searchTextChange(searchText)" ...>
  <md-not-found>
    <span ng-click="ok()">Click here to create new item</span>
  </md-not-found>
</md-autocomplete>

$scope.ok = function() {
  document.querySelector('md-virtual-repeat-container').classList.add('ng-hide');
};

$scope.searchTextChange = function() {
  document.querySelector('md-virtual-repeat-container').classList.remove('ng-hide');
};

[Tarpsvo]

@dominicgoulet @nestorneto
I had to combine both of your solutions to get the hack working. Thanks guys.

Eagerly waiting for a fix.