Skip to content

v4: Forms cleanup #19141

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

Merged
merged 34 commits into from
May 11, 2016
Merged

v4: Forms cleanup #19141

merged 34 commits into from
May 11, 2016

Conversation

mdo
Copy link
Member

@mdo mdo commented Feb 9, 2016

This branch aims to overhaul a decent amount of forms styles and documentation with the hopes of getting it near final. It's still WIP and has a few more todos (noted below).

Quick screenshot

screen shot 2016-02-09 at 1 06 30 am

Changes

Todos

mdo added 8 commits February 9, 2016 00:34
- Add container to fix padding in mobile views
- Add large and small variations
- Cross link grid classes and mixins
- Fix up some words
Uses a new more specific class, adds some basic spacing, and clarifies
that this class is only for validation feedback.

Clears up the help text class question in
#18704 (comment) and
addresses the vertical spacing in #18703.
- Give some guidance on when someone might use any of the three
validation states. Fixes #18702.

- Improve the examples to provide examples of supporting validation
text with the new `.form-control-feedback`, as well as always-present
help text. Nullifies #18704.
@mdo mdo added this to the v4.0.0-alpha.3 milestone Feb 9, 2016
@petetnt
Copy link
Contributor

petetnt commented Feb 9, 2016

There's also this (again) #19004 but that might require revisiting all the $brand-colors

@mdo
Copy link
Member Author

mdo commented Feb 9, 2016

@petetnt I'll add it to the todo list and see what I can do :).

@patrickhlauke
Copy link
Member

Note #19277 which supersedes #17266

mdo added 6 commits April 23, 2016 14:24
- Rather than use CSS hacks, let's avoid needing to hack anything
- Creates a new Reboot entry to simply reset the appear of the temporal inputs, thereby avoiding the problem entirely
- Less than ideal for conveying affordance on iOS, but given bugginess of the input itself, seems a decent tradeoff
@mdo
Copy link
Member Author

mdo commented May 9, 2016

Decent update to this today:

Have some more fiddling to do yet, but getting there.

@mdo
Copy link
Member Author

mdo commented May 11, 2016

Got the bulk of this done, but still have more changes to do as follow-up.

@niftylettuce
Copy link

I see a lot of stuff is commented out, not sure where the issue is regarding this?

Screenshot:

screen shot 2016-07-17 at 4 58 32 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants