Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default property values not always respected #2

Closed
cvasseng opened this issue Sep 2, 2016 · 4 comments
Closed

Default property values not always respected #2

cvasseng opened this issue Sep 2, 2016 · 4 comments
Assignees
Labels

Comments

@cvasseng
Copy link
Contributor

cvasseng commented Sep 2, 2016

Defaults are not always set in the customizer.

@cvasseng cvasseng added the bug label Sep 2, 2016
@cvasseng cvasseng self-assigned this Sep 2, 2016
@cvasseng
Copy link
Contributor Author

cvasseng commented Sep 2, 2016

Seems to be caused by missing defaults in the API dump..

@cvasseng cvasseng closed this as completed Sep 2, 2016
@TorsteinHonsi
Copy link
Contributor

When you encounter these things, you can give me a notice, or update the API yourself. Any specific default missing?

@cvasseng
Copy link
Contributor Author

cvasseng commented Sep 5, 2016

I'll update my report script to look for missing defaults too.

@cvasseng
Copy link
Contributor Author

cvasseng commented Sep 5, 2016

(though as a side note, most of the defaults seem to in order; I was just expecting a couple to be something else than null, but null seemingly means auto/inherit for e.g css objects)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants