CSL308801: Avoid unwanted box model sizing issues in CSS
CSL308802: Avoid properties that don't work based with the display property being used in CSS
CSL308803: Avoid duplicate properties in CSS
CSL308804: Avoid un anchored hovers in CSS
CSL308805: Avoid empty rules in CSS
CSL308806: Use only known properties in CSS
CSL308807: Avoid adjoining classes in CSS
CSL308808: Avoid property box-sizing in CSS
CSL308809: Use compatible vendor prefixes in CSS
CSL308810: Use all gradient definitions in CSS
CSL308811: Avoid negative text indent in CSS
CSL308812: Use standard property with vendor prefix in CSS
CSL308813: Use fallback colors in CSS
CSL308814: Avoid star hack in CSS
CSL308815: Avoid underscore hack in CSS
CSL308816: Use bulletproof font face in CSS
CSL308817: Do not use too many web fonts in CSS
CSL308818: Do not use @import in CSS
CSL308819: Avoid selectors that look like regular expressions in CSS
CSL308820: Do not use universal selector in CSS
CSL308821: Do not use unqualified attribute selectors in CSS
CSL308822: Do not use units for zero values in CSS
CSL308823: Avoid overqualified elements in CSS
CSL308824: Use shorthand properties in CSS
CSL308825: Do not use duplicate background images in CSS
CSL308826: Avoid too many floats in CSS
CSL308827: Do not use too many font size declarations in CSS
CSL308828: Do not use IDs in selectors in CSS
CSL308829: Do not use !important in CSS
CSL308830: Do not use outline:none in CSS
CSL308831: Do not use qualified headings in CSS
CSL308832: Define headings only once in CSS
Expand Minimize

CSL308826: Avoid too many floats in CSS

This rule is aimed at reducing complexity by watching how many times float is used. It warns when float has been used more than 10 times. This amount of floats usually indicates that there are a lot of columnar layouts being defined and that a grids system would be a better choice for your CSS.

CheckId CSL308826
TypeName AvoidTooManyFloatsInCSS
Severity Warning
Type CSSFile
See also
Disclaimer: The views and opinions expressed in this documentation and in SPCAF do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. SPCAF and RENCORE are registered trademarks of Rencore. All other trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.