From: Mark Otto Date: Tue, 16 Jan 2018 05:44:04 +0000 (-0800) Subject: Mention .input-group-text in migration docs (#25325) X-Git-Tag: v4.0.0~16 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d16eb10e494cdc1531c7938f6cb54d47ec13e3cc;p=thirdparty%2Fbootstrap.git Mention .input-group-text in migration docs (#25325) Closes #25231 --- diff --git a/docs/4.0/migration.md b/docs/4.0/migration.md index 0ec2773c45..9b4030699d 100644 --- a/docs/4.0/migration.md +++ b/docs/4.0/migration.md @@ -31,7 +31,7 @@ While Beta 2 saw the bulk of our breaking changes during the beta phase, but we ### Input groups -- Input group addons are now specific to their placement relative to an input. We've dropped `.input-group-addon` and `.input-group-btn` for two new classes, `.input-group-prepend` and `.input-group-append`. You must explicitly use an append or a prepend now, simplifying much of our CSS. +- Input group addons are now specific to their placement relative to an input. We've dropped `.input-group-addon` and `.input-group-btn` for two new classes, `.input-group-prepend` and `.input-group-append`. You must explicitly use an append or a prepend now, simplifying much of our CSS. Within an append or prepend, place your buttons as they would exist anywhere else, but wrap text in `.input-group-text`. - Validation styles are now supported, as are multiple inputs (though you can only validate one input per group).