New issue
Advanced search Search tips

Issue 801069 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 545318



Sign in to add a comment

[css-typed-om] Check that we don't crash with null pointer errors

Project Member Reported by shend@chromium.org, Jan 11 2018

Issue description

We should add some tests that pass null into parts of the API. There are cases where it doesn't make sense to test, e.g.

     new CSSKeywordValue(null);

since the IDL says CSSKeywordValue expects a string and the bindings code will automatically convert null into "null" anyway. But we should test cases where it is "valid" to pass a null to see if our code correctly handles it. For example, CSSVariableReferenceValue.fallback can be null and we have tests for that.
 

Comment 1 by shend@chromium.org, Feb 6 2018

Status: WontFix (was: Available)
I think we've already covered all the null cases correctly.

Sign in to add a comment