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

Use postcss warnings to unfixable bugs #17

Open
kadmil opened this issue Jun 24, 2015 · 4 comments
Open

Use postcss warnings to unfixable bugs #17

kadmil opened this issue Jun 24, 2015 · 4 comments

Comments

@kadmil
Copy link
Contributor

kadmil commented Jun 24, 2015

There are things we can't fix on css-only level. For such problems we could generate warnings with postcss API https://github.com/postcss/postcss/blob/master/docs/api.md#warning-class

Thank @ai for suggesting this. )

@luisrudge
Copy link
Owner

You mean for bugs that we can't evaluate if width or height, for example?

@kadmil
Copy link
Contributor Author

kadmil commented Jun 24, 2015

Yep, like this. Or if we detect config which is known to cause bugs and can't fix them on css-only level
https://github.com/philipwalton/flexbugs/blob/master/README.md#2-column-flex-items-set-to-align-itemscenter-overflow-their-container

@MoOx
Copy link

MoOx commented Jun 30, 2015

👍

@cvrebert
Copy link

Can this qualify as a flexbug for the purposes of warning about it?: https://drafts.csswg.org/css-flexbox/#item-margins

Authors should avoid using percentages in paddings or margins on flex items entirely, as they will get different behavior in different browsers.

[Edit: Ah, #12]

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

No branches or pull requests

4 participants