-
Notifications
You must be signed in to change notification settings - Fork 16
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
Remove global box-sizing and universal selector #2
Comments
Hi, Interesting point but the default box sizing is not really intuitive and almost every framework and dev use box-sizing and it's available almost everywhere but I am open to the idea. Concerning the performance, I quote Paul Irish
|
It isn't. I agree. But it is default and here is a point. Now we, developers, separated into two camps, like Villariba and Villabajo. And sometimes we need to work together, our plugins and frameworks have to work together as well. Only one way to do it is to use standards, specifications and defaults. What for universal selector it is not a big disadvantage, but still disadvantage :) |
From the other side if you use default |
Just my 2 cents. Every framework is and should be opinionated. You can not fit to every case possible with it. So if you don't like the default behaviour, you customize it for your needs. Especially if the code base is that small. |
Thanks for your feedbacks. I agree with @roxkisrover, I think that it is impossible to please everybody and in my humble opinion, I prefer |
@BafS it is up to you of course, but you get it wrong. In case of framework you can please everybody. Just don't change default |
Hello.
Maybe it is not such a good idea to use
box-sizing: border-box
globally. Should use it only where it is needed. Let's keep it as defaultcontent-box
because this is what developers expect.The universal selector is know to be slow and this is agains motherfucking ideas.
Here is a pull request.
The text was updated successfully, but these errors were encountered: