Mark invalid values as parse errors in DevTools for registered custom properties |
|
Issue descriptionChrome Version: 69 What steps will reproduce the problem? (1) Enable flag chrome://flags/#enable-experimental-web-platform-features (2) Visit http://jsfiddle.net/z8tn1ruo/4/ (3) Inspect blue square. What is the expected result? "--test: invalid" should be crossed out like "color: invalid" What happens instead? "--test: invalid" shows up as if it's accepted by the syntax. Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jul 9
Thanks for considering this! |
|
►
Sign in to add a comment |
|
Comment 1 by paulir...@chromium.org
, Jul 9Status: Assigned (was: Untriaged)