ngf-change gets called as soon as button is clicked

[lookfirst]

The documentation suggests that ngf-change would be called after the files are selected in the chooser dialog. Right now, it gets called as soon as the button is clicked.

[deckikwok]

You are right though I wont say it's an error. I believe if your model did not specify null initially then a 'change' would have been detected. For now, you can do an if (file && file.length)

[danialfarid]

Updated the wordings in the doc.

[lookfirst]

Please re-open. This can't possibly be the intended behavior. Not only does it fire before the file chooser opens, but also after.

[danialfarid]

Yea I explained it in the docs, it will be called when the files selected or cleared by clicking on the button.

[lookfirst]

@danialfarid What I'm seeing is that ngf-change is being called TWICE. Once when you click the button and the file chooser dialog opens and once when the dialog closes after selecting a file.

I added this to your fiddle...

    $scope.upload = function (files) {
        alert('called from upload. files is: ' + files);

Whatever is calling it shouldn't call it the first time. There is no reason to call $scope.upload if files is null. This would allow me to remove the null check and simplify things greatly.

[danialfarid]

I explained on my first comment why it needs to be set to null when you click on it. So it is expected behaviour.

[lookfirst]

It doesn't need to fire.

[danialfarid]

#764