Add more descriptive placeholder text to the Send Feedback from initiated from the Sad Tab |
||||||||||||
Issue descriptionFeature description: Most feedbacks submitted from the Sad Tab do not provide any useful information (e.g. reproducible steps). This would add a more prescriptive placeholder text into the Send feedback form to prompt for more useful feedback. Change header from "Tell us what's happening" to "Describe what you were doing when Chrome crashed" Change placeholder text from "Tab crashed feedback" to "Help our engineers investigate and fix this crash. List exact steps if you can. No detail is too small!" Eng owner: pamg Product owner: yyushkina, srahim Design doc: None, string change only Are you planning on experimenting before launch? No Any new strings? Yes Any implications for Google webservices (i.e. sync, translate)? No Binary size? N/A Do the existing perf tests exercise all aspects of your new feature(s)? Yes
,
Apr 12 2017
,
Apr 15 2017
Are you planning on changing feedback for Android as well or only desktop?
,
Apr 15 2017
The plan is to this on all platforms
,
Apr 18 2017
How do you plan on modifying the feedback form on Android? AFAIK, we don't control the UI for the feedback form. The feedback team controls that part.
,
Apr 18 2017
I'll check with Matt (PM for Feedback).
,
Apr 18 2017
,
Apr 18 2017
,
Apr 21 2017
,
Apr 21 2017
,
Apr 24 2017
,
Apr 24 2017
,
Apr 24 2017
As per Matt, Android does not support customization of the form.
,
Apr 24 2017
,
May 17 2017
Hey Ahmed, I wanted to check with you when you might be able to land this string change? It would be amazing to have in before branch.
,
May 18 2017
I'm the primary Chrome OS gardener this week, so I might not get to it this week, but I'll get it before branch.
,
May 18 2017
Awesome thanks!
,
May 22 2017
,
May 22 2017
Shouldn't it be "Describe what you were doing when *the tab* crashed"? "the tab" instead of "Chrome"?
,
May 22 2017
Yep, good call, let's do that.
,
May 22 2017
Perfect.
,
May 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b47d9268ef018f9ed66378c33b317d9a4cb3553e commit b47d9268ef018f9ed66378c33b317d9a4cb3553e Author: afakhry <afakhry@chromium.org> Date: Thu May 25 02:42:49 2017 More descriptive feedback description in feedbacks filed from the SadTab page We're working to encourage our users to give us more helpful feedback instructions as to how to repro any crashes in the renderers. Screenshot: https://bugs.chromium.org/p/chromium/issues/detail?id=710221&desc=2#c21 BUG= 710221 TEST=Go to chrome://crash and file a feedback from there and make sure to see a more descriptive title and placeholder text. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2900643004 Cr-Commit-Position: refs/heads/master@{#474533} [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/app/generated_resources.grd [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/browser/extensions/api/feedback_private/feedback_private_api.cc [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/browser/feedback/show_feedback_page.cc [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/browser/resources/feedback/js/data.js [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/browser/resources/feedback/js/event_handler.js [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/browser/resources/feedback/js/feedback.js [modify] https://crrev.com/b47d9268ef018f9ed66378c33b317d9a4cb3553e/chrome/common/extensions/api/feedback_private.idl
,
May 25 2017
,
Jun 5 2017
FYI. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by yyushkina@chromium.org
, Apr 12 2017