Closed
Bug 931189
Opened 12 years ago
Closed 12 years ago
fix feedback forms to be in line with 10k character max for description
Categories
(Input Graveyard :: Submission, defect, P3)
Input Graveyard
Submission
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
Details
(Whiteboard: u=user c=feedback p=2 s=input.2013q4)
Bug #929664 had us add a 10,000 character max for the description. However, there's no indication in the feedback form that the user's comment will be truncated.
This bug covers fixing that.
Assignee | ||
Comment 1•12 years ago
|
||
Making this a P3 since this is kind of an edge case--not many people go over 10,000 characters so we can punt on it for a while.
Adding it to the current quarter queue.
Priority: -- → P3
Whiteboard: u=user c=feedback p= s=input.2013q4
Assignee | ||
Comment 2•12 years ago
|
||
Possible options:
1. JavaScript code to show the current character count and maximum character count and when the current is over the maximum, prevent the form from being submitted and make the text box red. Or some similar no-new-strings ux.
2. When the user submits a form with a description with more than 10,000 characters, return an error saying the description is too long. We can do this with the existing ResponseForm. This requires strings changes, though this might be an edge case so the fact it requires strings changes might not matter a whole lot.
Are there other things we could/should do?
Assignee | ||
Comment 3•12 years ago
|
||
I just did something similar with the Firefox OS feedback form where it disables the submit button and puts a red border around the description when it's over the character max. That coupled with a character counter should cover all the issues here "good enough" without requiring any strings changes.
One note is that the character counter should work correctly for both RTL and LTR.
I think that's about 2 points of work. Marking it as such.
Whiteboard: u=user c=feedback p= s=input.2013q4 → u=user c=feedback p=2 s=input.2013q4
Assignee | ||
Comment 4•12 years ago
|
||
I added a max character count and a counter (part of the code was already there).
PR: https://github.com/mozilla/fjord/pull/199
This doesn't involve any l10n changes, so it can go through. Also, it doesn't prevent the form from being submitted. I decided that with the visual indicator plus the fact that we truncate the description if it's too long on the backend, the extra validation and messaging code wasn't really needed and is easy to get around by miscreants anyhow.
Assignee | ||
Updated•12 years ago
|
Summary: fix feedback form to be in line with 10k character max for description → fix feedback forms to be in line with 10k character max for description
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•12 years ago
|
||
Landed in master in:
https://github.com/mozilla/fjord/commit/db2a2d3
https://github.com/mozilla/fjord/commit/fd7c877
https://github.com/mozilla/fjord/commit/6f64900
It's not great, but it's good enough. I look forward to the day when we can fix/redo these feedback forms.
Pushed to production just now.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•