(in many cases anyway, there might be a reason for *some* fields not to submit with Enter but I'd need to be convinced case by case)
2020-09-27 27135, 2020
Mr_Monkey has quit
2020-09-27 27135, 2020
Mr_Monkey joined the channel
2020-09-27 27127, 2020
chaban has quit
2020-09-27 27141, 2020
chaban joined the channel
2020-09-27 27153, 2020
Mr_Monkey
For free text forms we won't want enter to submit, that's the easy example.
2020-09-27 27153, 2020
Mr_Monkey
For the fancy search selects we use that allow to write text (that alias language select for example), using spacebar to select isn't available (the user can input text) and they use enter to open the select and confirm the selection of an item.
2020-09-27 27153, 2020
Mr_Monkey
For all other fields, I don't see why not. I hadn't realized they weren't behaving like standard inputs.
2020-09-27 27138, 2020
Mr_Monkey
I think the issue is that each section in the edit page is a separate component, and they are not part of one single parent <form> html element, which should trigger the normal behavior.
2020-09-27 27149, 2020
reosarevok
Free text forms are perfectly fine for enter to submit *except* the ones where you want multilines. Say, name? enter to submit. Annotation? no.
2020-09-27 27107, 2020
Mr_Monkey
Yes, we're on the same page.
2020-09-27 27120, 2020
CatQuest
totes
2020-09-27 27126, 2020
CatQuest
btw. Mr_Monkey looking at tickets I think ww need a "badge/achievement" component
2020-09-27 27126, 2020
CatQuest
also a a "search" one
2020-09-27 27126, 2020
CatQuest
another thing i thought of was to make all tickets about problems with search, subtickets of a master "fix elasticsearch" ticket
