Closed
Bug 1046738
Opened 10 years ago
Closed 9 years ago
How should we notify the user when feedback data sending fails?
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
WONTFIX
backlog | - |
People
(Reporter: NiKo, Unassigned)
References
Details
Attachments
(1 file)
112.82 KB,
image/png
|
Details |
This is related to bug 972992; we don't have UX spec for when sending the feedback data possibly fails. - Should we display a notification? Where? - Should we rather update the "Thank you" screen? - Should we just log the error to the browser console and keep going?
Comment 2•10 years ago
|
||
Personal opinion I think we should just log the error to the browser console and keep going. Users know we won't get back to them when they submit feedback and they should not be bothered by error messages if they are kind enough to provide feedback so I think we may want to implement a retry in the background (probably not FF34 though) but we don't want to display an error message to the user.
Comment 3•10 years ago
|
||
Not a bad option to fail silently as RT proposes. If we want to allow a retry we could do something like the attached flow.
Flags: needinfo?(dhenein)
Comment 4•10 years ago
|
||
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Darrin Henein [:darrin] from comment #4) > Created attachment 8465600 [details] > feedback-retry.png This <3 (personal opinion too).
Comment 6•10 years ago
|
||
OK, let's implement a silent failure for now as I am not convinced a notification is needed from a user standpoint. This also seems to have the benefit of involving less work at a time where we should try restricting the scope. We can revisit later if we find that this is a useful feature. I am therefore marking this as a client backlog dependency.
Updated•10 years ago
|
backlog: --- → -
Comment 7•9 years ago
|
||
changing way we collect feedback to NPS - no longer relevant
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•