Closed
Bug 1223495
Opened 10 years ago
Closed 10 years ago
String handling bug in form.creative on BMO
Categories
(bugzilla.mozilla.org :: Custom Bug Entry Forms, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mhoye, Assigned: dkl)
Details
In:
https://bugzilla.mozilla.org/form.creative
... if I put my email address in the last field, it will fail saying that there's no match for "mhoye@mozilla.comsmartell@mozilla.com"
If I instead put in "mhoye@mozilla.com, " with the comma space at the end, everything works fine.
| Assignee | ||
Comment 1•10 years ago
|
||
(In reply to Mike Hoye [:mhoye] from comment #0)
> In:
>
> https://bugzilla.mozilla.org/form.creative
>
> ... if I put my email address in the last field, it will fail saying that
> there's no match for "mhoye@mozilla.comsmartell@mozilla.com"
>
> If I instead put in "mhoye@mozilla.com, " with the comma space at the end,
> everything works fine.
I am not sure what is wrong here. The comma is added automatically by the autocomplete JS so why remove it and the spaces? If I do "mhoye@mozilla.com, smartell@mozilla.com" in the text field the form submits fine.
dkl
Flags: needinfo?(mhoye)
| Reporter | ||
Comment 2•10 years ago
|
||
I don't know what's happening; all I've got is the error I described, and how I resolved manually; if add _only_ mhoye@mozilla.com then the error message I get says "mhoye@mozilla.comseanmartell@mozilla.com", even if I haven't added Martell's address.
Flags: needinfo?(mhoye)
| Assignee | ||
Comment 3•10 years ago
|
||
There is an issue in thet JS when clicking the "Mozilla Creative Collective" checkbox and adding a POC account without the ending comma. Fix coming.
Assignee: nobody → dkl
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•10 years ago
|
||
Will be in the next prod code push.
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
a0e7a4f..b4bfae7 master -> master
dkl
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 5•10 years ago
|
||
Thanks very much!
You need to log in
before you can comment on or make changes to this bug.
Description
•