Pavel Blagodov We discussed this during Eventing scrum today. And it appears we are out of our depth in figuring out why this is happening. May I request your help on this one? Thank you!

A quick update on what I found out before hitting my depth with the frontend:

In the "Add Functions" page, if any of the <input type="text" / type="number" / type="password" such as following:

https://github.com/couchbase/eventing/blob/master/ui/eventing-ui/ui-current/fragments/app-settings.html#L156

receives an "Enter" keypress event, it appends a new binding object to the $self.bindings variable, which is then rendered here :

https://github.com/couchbase/eventing/blob/master/ui/eventing-ui/ui-current/fragments/app-settings.html#L364

—

So simplify, insert any <input type="text"> element in the form and send a keypress Enter event which appends a new binding to the bindings array.

Hello Jeelan Poola, Sujay Gad, Abhishek Jindal

What is the expected behaviour when user presses ENTER? (besides not adding a new Binding)

We could:

• do nothing or
• submit the form and close the dialog - same behaviour as clicking on Next: Add Code

Raluca Lupu Enter shouldn't do anything. need to somehow suppress whatever event it is generating and adding bindings.
Form should only be submitted on "Add Code".

Thank you Abhishek Jindal, I've just push a patch with this behaviour.

Build couchbase-server-7.1.0-2285 contains eventing commit 23c2faa with commit message:
MB-49339: Add Function dialog: don't add bindings on ENTER

Validated the fix on Enterprise Edition 7.1.0 build 2285.