Closed LukeAskew closed 11 years ago
@awood1261 @apartyka Thoughts?
Any time I ever see a unit attached to 0 I remove it. 0 is 0. There is no need to attach the unit.
Sidenote: I once found/replaced 200+ declarations of "0px" from a style sheet over 1000 lines long. It cut down around 140kb. So, one could argue for not adding it for optimization's sake.
I agree with the zero policy. One possible exception?
border: 0 none;
On Fri, Jul 26, 2013 at 12:56 PM, apartyka notifications@github.com wrote:
Any time I ever see a unit attached to 0 I remove it. 0 is 0. There is no need to attach the unit.
Sidenote: I once found/replaced 200+ declarations of "0px" from a style sheet over 1000 lines long. It cut down around 140kb. So, one could argue for not adding it for optimization's sake.
— Reply to this email directly or view it on GitHubhttps://github.com/LukeAskew/Front-End-Standards/issues/47#issuecomment-21633720 .
@mrbinky3000 Does that not work? What is the exception?
not an exception, I guess. 0 has no unit and "none" is in relation to the border type. So, not a problem.
On Fri, Jul 26, 2013 at 1:16 PM, LukeAskew notifications@github.com wrote:
@mrbinky3000 https://github.com/mrbinky3000 Does that not work? What is the exception?
— Reply to this email directly or view it on GitHubhttps://github.com/LukeAskew/Front-End-Standards/issues/47#issuecomment-21634925 .
it's should just be 0
, @mrbinky3000 is correct
For CSS standards, you should not use units when the value is
0
.Proposed standard:
Avoid using units when declaring
0
as a value.