[Tickets #12932] Re: Avoid save event pressing ENTER key while tag or attendee editing

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12932
------------------------------------------------------------------------------
  Ticket             | 12932
  Updated By         | almarin at um.es
  Summary            | Avoid save event pressing ENTER key while tag or
                     | attendee editing
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


almarin at um.es (2014-01-29 10:20) wrote:

>> With my patch, hitting RETURN
>> doesn't save the event but finish editing mode of tag/attendees, so
>> the last tag/attendee is properly included in the final list.
>
> That's what I'm saying. It DOESN'T fix this issue. If you are still  
> typing the tag name before typing a comma (and thus still inside the  
> hidden text field), hitting ENTER still saves the event - and  
> without the tag being saved entered

It does, at least in my side. With my patch, hitting ENTER before  
typing a comma the input field disappear, the tag/attendee is included  
in the list ( I can even see the freebusy info of that last attendee)  
and then clicking "save event" button, last tag/attendee is saved with  
the event (and invitations are properly sent).

Anyway, I don't want to put the focus on my patch, probably it is only  
a fast/dirty way to prevent this issue (i insist, it works for me) and  
I agree with you that it breaks the common input behaviour.

Let's put the focus in the issue that hitting enter before typing a  
comma doesn't save the last tag/attendee. It is very frustrating  
specially with attendees, because invitation is not sent to the last  
attendee if you forget to put a comma or blur the input.
>
>
>> I agree with you when you say that all fields should behave the same
>> way, but at least this issue should be resolved.
>>
>> Thanks
>>
>>