Closed Bug 822512 Opened 12 years ago Closed 11 years ago

Feedback on form error doesn't update properly

Categories

(Marketplace Graveyard :: Consumer Pages, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
2013-01-10

People

(Reporter: dbialer, Assigned: potch)

Details

Feedback from user.

Using desktop verion.

Hi, there is a minor bug in the UI of comment section for an app. Steps to reproduce

1) Write a long comment (>150 chars, say 163 chars)
2) Select a big section and delete it.
3) Write a smaller text so that the comment stays <150 chars

What to note: the error message in the bottom left (in red text) is still not updated. It still says the value should be 150 chars long but is 163 chars long. The length displayed in bottom right is correctly updated though.
Summary: Feedback form error form doesn't update properly → Feedback on form error doesn't update properly
potch is messing with the feedback flow already so giving to him
Assignee: nobody → thepotch
Target Milestone: --- → 2013-01-03
The error form only updates on submission. If you don't press Submit again, the error will not update. Is this what you are experiencing?
Target Milestone: 2013-01-03 → 2013-01-10
I received this through the feedback mechanism from a b2g tester so am kind of re-reporting it.  Looking at the bug again, it is a bit ambiguous. I tried it and you are correct.  When you clear the display, it resets the character count but doesn't reset the error message.  Not really an error and perhaps it is up to interpretation what the correct behavior is.  I would ask UX to look at.
(In reply to Potch [:potch] from comment #2)
> The error form only updates on submission. If you don't press Submit again,
> the error will not update. Is this what you are experiencing?

If that's the case I'm willing to wontfix this.  UX can get back to us if they want to tweak it.  Thanks for investigating.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.