mirror of
https://github.com/twbs/bootstrap.git
synced 2022-11-09 12:25:43 -05:00
fix #11144
This commit is contained in:
parent
a28b2cb9e1
commit
25b7a5200d
1 changed files with 1 additions and 1 deletions
|
@ -39,7 +39,7 @@ We only accept issues that are bug reports or feature requests. Bugs must be iso
|
||||||
|
|
||||||
- Adhere to the [RECESS CSS property order](http://markdotto.com/2011/11/29/css-property-order/)
|
- Adhere to the [RECESS CSS property order](http://markdotto.com/2011/11/29/css-property-order/)
|
||||||
- Multiple-line approach (one property and value per line)
|
- Multiple-line approach (one property and value per line)
|
||||||
- Always a space after a property's colon (.e.g, `display: block;` and not `display:block;`)
|
- Always a space after a property's colon (e.g., `display: block;` and not `display:block;`)
|
||||||
- End all lines with a semi-colon
|
- End all lines with a semi-colon
|
||||||
- For multiple, comma-separated selectors, place each selector on its own line
|
- For multiple, comma-separated selectors, place each selector on its own line
|
||||||
- Attribute selectors, like `input[type="text"]` should always wrap the attribute's value in double quotes, for consistency and safety (see this [blog post on unquoted attribute values](http://mathiasbynens.be/notes/unquoted-attribute-values) that can lead to XSS attacks).
|
- Attribute selectors, like `input[type="text"]` should always wrap the attribute's value in double quotes, for consistency and safety (see this [blog post on unquoted attribute values](http://mathiasbynens.be/notes/unquoted-attribute-values) that can lead to XSS attacks).
|
||||||
|
|
Loading…
Reference in a new issue