Issue metadata
Sign in to add a comment
|
Chrome bug reporting wizard does not allow filing CSS bugs
Reported by
fanta...@gmail.com,
Mar 14 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 Steps to reproduce the problem: 1. Go to https://bugs.chromium.org/p/chromium/issues/list 2. Click on New Issue 3. Click Next 4. Click Web developer 5. Try to figure out whether layout bugs belong under “API”, “JavaScript”, or “Developer Tools” What is the expected behavior? UI presents an option to report bugs against the layout engine. What went wrong? UI designer assumed web development only consists of JavaScript APIs. Did this work before? Yes Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: Flash Version:
,
Mar 16 2017
Reporter@ could you please file this issue in Monorail tracker. https://bugs.chromium.org/p/monorail/issues/list Thanks.
,
Mar 17 2017
If there's a layout bug, you can file it under the component: "blink>layout". Blink is our web browser engine that handles layout, etc.
,
Mar 20 2017
I filed it over at monorail as requested. https://bugs.chromium.org/p/monorail/issues/detail?id=2459 The status on this bug should be Out Of Scope, not Wontfix or Invalid or something, as I really hope it will be fixed. > If there's a layout bug, you can file it under the component: "blink>layout". Blink is our web browser engine that handles layout, etc. The point of this bug is that I would have to guess that “Blink > Layout” is considered an “API” component and select that option in the bug reporting interface before I could even see it as a possibility, and this makes the reporting interface very confusing because I would never make such a guess. You could have a very interesting discussion about whether CSS is in fact an API, but afaik nobody in Web development really thinks of it as such. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Mar 15 2017