$(...).trigger('change') will not update data-linked value after commit 84

[shimooka]

Hi.

Is there any solution ?

• commit 83 : https://jsfiddle.net/shimooka/1bsr3szf/ ===> when click 'trigger' button, update input tag and text.
• commit 84 : https://jsfiddle.net/shimooka/69pcrg1s/ ===> when click 'trigger' button, update input tag ONLY.

-=-=-=-=-=-=-

I try to use EmojiOneArea (https://github.com/mervick/emojionearea) with jsviews, and EmojiOneArea seems like use trigger() when updateing a input tag .

[BorisMoore]

Yes, that is deliberate. If you use the default trigger=true setting, then updates happen after each keyDown event. But then you don't want an additional update to happen on the blur/change event. So the trigger() or change() action is skipped. (Prior to commit 84 the change handler was getting called twice - once after keyDown once on blur/change.)

If you want to be able to enable using trigger() - so EmojiOneArea works, you can disable the async trigger. Either set $.views.settings.trigger(false) globally, or on the specific input:

<input type="text" id="label" data-link="label trigger=false"/>

Now updating will only happen on blur, but trigger() will work.

UPDATE: If that does not suffice for your needs, you can use trigger='change keyup' - see comment below...

[shimooka]

Hi Boris !

I will try to use 'trigger=false' . thanks for your reply :-)

[BorisMoore]

Oh - by the way, another option is to write

<input type="text" id="label" data-link="label trigger='change keyup'"/>

or $.views.settings.trigger("change keyup");

With that setting and trigger/blur/change will work as well as updating on keyup (which is a slightly less good as a user experience than the async keydown you get when trigger is set to true, but may still be a good experience for your needs...)