Added pure-help-block

[its-danny]

I noticed there's already a pure-help-inline, so I went ahead and added a block version. Might be useful to have them in the docs as well, I use them quite a bit when using Bootstrap.

[tilomitra]

Thanks, this is helpful. I'll pull this down and test it locally.

[tilomitra]

@dannytatom This looks good. I'm pulling it in, but I changed .pure-help-block, to just .pure-help. Objections?

[its-danny]

Looks better to me, I went with -block only because the other is -inline.

[tilomitra]

I think we can assume *-block by default. I also removed the margins because it seems to work better without it. It's closer to the actual input element. Otherwise, the pure-help-inline and pure-help don't have equal margins on small screens (because the pure-help-inline doesn't have a default margin. Here's how it looks now:

/* Block help for forms */
.pure-form .pure-help {
  display: block;
  color: #666;
  font-size: 90%;
}

[its-danny]

Looks good to me, thanks for the rundown. 😀

[tilomitra]

@dannytatom Thanks dude. Would you mind signing this CLA so that I can merge this in? We need a signed CLA to merge stuff in. I'm going to add this to the README.md.

[its-danny]

@tilomitra Signed! And no problem, hopefully I can get around to working a bit more on it, huge fan so far.

[ericf]

@tilomitra pure-help doesn't signal to me what it actually does. I feel that pure-inline and pure-block are much more helpful and could be used outside of a descendent pure-form selector. That said, do we really need this at all, if they are going to be scoped to forms, then couldn't we have pure-form-inline?

[tilomitra]

@ericf So pure-form-help-inline and pure-form-help? pure-form-inline can be confused with the inline form.

[ericf]

Remove "help" it's meaningless. Pure's whole goal is to "help" :P

[its-danny]

I think it makes sense to be there, as it's used (at least inline is) to give a tip about the form element it's next to or under. pure-block and pure-inline sound like they're alignment classes.

[ericf]

So again, my vote on naming is here: #32 (comment)

[tilomitra]

I agree with @dannytatom that pure-block and pure-inline don't work. help by itself would be vague, which is why I am suggesting pure-form-help-inline and pure-form-help/pure-form-help-block.

If "help" is an issue, we can change it to "message":

• pure-form-message-inline
• pure-form-message

[ericf]

Ah, okay, I wasn't understanding "help" I thought it meant, help-make-forms-inline. I see now that it's for help text directed at the person using the form :)

I think "message" is better and clearer that it has nothing to do with CSS, but rather helping layout a part of form, the text to help the user fill out the form.

[tilomitra]

So are we cool with pure-form-message-inline and pure-form-message? I can make the appropriate changes to @dannytatom's commit and merge it in.

[ericf]

@tilomitra I am. Be sure to update the HISTORY.md with a (!) to signal possible back-compat breakage. And on that note, we should leave in (but mark as deprecated) the pure-help* selectors.

[tilomitra]

@dannytatom Thanks dude. Merged and closed.

[freshface]

Is it possible to provide an example on how to use these classes?

[ghost]

@freshface You can find many examples on the project's website at http://purecss.io