Textangular box not getting model changes

[worldspawn]

I have a model that looks a bit like:

{ comments : null }

This is referenced like so:

<div text-angular ng-model="commentResource.comment" id="description" name="description"></div>

Now i recreate the commentResource

$scope.commentResource = new commentResource();

The value shown in the text angular box is not updated. I've tried with a normal input type=text and the value is updated. I can work around this by explicitly setting the comment field to null after recreating the model... which is weird :)

$scope.commentResource = new commentResource();
$scope.commentResource.comment = null; //textangular binding issue

[mbarzeev]

+1

[mbarzeev]

It seems to be a focus issue of the editor.
removing the focus (any focus for that metter) before I've updated the model seemed to solve it, like so:

$( ":focus" ).blur();

Hope it helps.

[worldspawn]

I'm updating model in response to a button click so the text angular widget should have already lost focus no? Or are you saying we just need a blur event somewhere (anywhere) in the dom?

[mbarzeev]

For me, pressing a different nested element on the view surprisingly didn't blurred the editor (see if it has the focus border to make sure).
Try what I've suggested above.

[SimeonC]

Quick note - I have the fix prepped and will commit it when I can, internet is sporadic while I'm in India till the end of Jan. The issue is with the checks that prevent it from updating when ng-model is undefined. Removing those if statements seems to fix the issue but I have to go back and figure out why it was there in the first place.

[SimeonC]

@matti I think the reason the editor toolbar buttons don't blur the editor is that they have unselectable set on them, else you wouldn't be able to keep typing after pressing one of the buttons.

[matti]

@SimeonC I believe you meant @mbarzeev

[mbarzeev]

hmmm... I don't think so ;)

[SimeonC]

@matti yea thanks, It was a guess from the email name that came through.

@mbarzeev The focus issue is possibly unrelated, once the undefined bug is fixed clicking on a button that uses ng-click will clear the editor correctly due to the $digest that gets triggered. There's code in place to try prevent blur being triggered on the editor when an editor toolbar button is pressed (I assume this is what you meant by nested element on the view). If this isn't the case could you open a new issue with how to replicate it please?

[mbarzeev]

Nop, I didn't mean the toolbar buttons (they work as expected as far as I can tell), I'm talking about an issue where a nested element, external to the editor altogether, did not remove the focus from the editor itself. Weird, I know...
I don't believe I will have the time to create a nice Fiddle example, and I found a workaround (as mentioned above) which fixed it.
Still be be nice to know when the fix you we're referring to will be available.

Thanks for the help and responsiveness.

[worldspawn]

Hullo, thanks for the fix. Its working like a charm.