Issue metadata
Sign in to add a comment
|
Low quality of bug reproduction effort
Reported by
mr.ber...@gmail.com,
Nov 16 2016
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Sofari/537.36 Steps to reproduce the problem: 1. Report a bug with fairly specific reproduction steps What is the expected behavior? Someone @chromium.org reads your reproduction steps and follows them, allowing them to reproduce the bug. Optionally: If, as it can happen, repro steps are not accurate enough to be followed by a bot, but might still be interpreted correctly by a human being, the person trying to reproduce your bug puts some effort into trying to understand what your bug might have been, and figure out the steps to reproduce the bug. What went wrong? - People don't follow all your steps (e.g., Issue 651104) - People follow steps inaccurately (e.g, Issue 655159 ) - People follow all your steps, but they fail to see the obvious problem (e.g., Issue 489671) As an effect, you need to work with these people through several iterations, holding their hands while repeatedly guiding them through every single step. Did this work before? Yes Some years ago Chrome version: 53.0.2785.116 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Nov 17 2016