Question

It seems that when I am replying in a case, if I hit return while editing the to (or cc or bcc) field, the email is immediately sent and the case is closed. I find this extremely frustrating.

To duplicate the problem:

• go to a case that is open and has a correspondent
• click Reply
• click in To field (or Cc or Bcc)
• hit return

Actual: email is sent and case is closed

Expected: ideally: move focus to next field; otherwise: prompt user to confirm the sending of the email

If the browser focus was on one of the Send buttons then I would understand sending the email immediately. But I don't think I have ever used an email client that would send when hitting return in a To field.

Case FC1866921

Answer 1

Update:

This is fixed in the next FogBugz On Demand release.

---

Here's a Bugmonkey script that you can use to disable "send on return."

name:          !Return to Sender
description:   Don't send email when pressing Enter in the To, Cc, Bcc or Subject fields.
author:        Kevin Gessner, Michel de Ruiter
version:       1.1.0.0

js:

$('#bugviewContainerEdit').on('keydown', '.emailHeader input', function(e) {
  if (!e.which || e.which === 13)
    return false;
});

Answer 2

Similar issue from a developer on our team, who is closing cases that he intended to resolve:

I was hitting return with the intention of submitting the form. In general, hitting return in any field in a form will activate the first submit button in the form. The problem I had is that sometimes the Resolve form has only "Resolve" and "Cancel" buttons and sometimes it also has a "Resolve and Close" button before the "Resolve" button. So sometimes hitting return would just resolve and sometimes it would resolve and close.

Answer 3

Hitting enter on a field to submit a form IS NOT STANDARD when the form has 1 main field, and the main field does not allow submitting with enter. Very few web pages behave this way, and fewer behave this way on purpose. This is annoying - I find it hard to believe anyone would expect this behavior.

As an alternative, I would also like to suggest changing the default button to "Cancel" instead of "Send" or "Send and Close". Losing what I typed would be annoying, but sending something I didn't mean to could cost me my job.

Answer 4

Really poor UI interactions like this are the reason my team hates this product (and is probably going to transition).