Add UX (User Experience) Category to Bug Tracker
Reported by
lmannin...@gmail.com,
Jun 14 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36 Steps to reproduce the problem: N/A What is the expected behavior? N/A What went wrong? While UX could broadly be grouped in with UI issues, I feel that UX and UI are not really the same thing. I would classify a UI issue as a technical problem with Chromium's UI, such as the Back button not working, whereas a UX issue would be a more usability problem such as the Back button works, but not as expected or could be improved to better satisfy users. Did this work before? N/A Chrome version: 51.0.2704.84 Channel: stable OS Version: Flash Version: Shockwave Flash 21.0 r0
,
Jun 15 2016
Confirming the issue as this is a feature request. Waiting for more inputs on this
,
Jul 5 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 30
Since this isn't a request from development who manages triaging issues it doesn't really match a component. However labels are generally used for this and labels are free form. |
||||
►
Sign in to add a comment |
||||
Comment 1 by thestig@chromium.org
, Jun 15 2016