New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 861613 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Mark invalid values as parse errors in DevTools for registered custom properties

Project Member Reported by alancutter@chromium.org, Jul 9

Issue description

Chrome 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.


 
Screenshot from 2018-07-09 11-29-11.png
238 KB View Download
Owner: einbinder@chromium.org
Status: Assigned (was: Untriaged)
Good idea.

This is part of the new CSS Properties & Values API, it seems: https://drafts.css-houdini.org/css-properties-values-api-1/


Thanks for considering this!

Sign in to add a comment