You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -1062,24 +1068,16 @@ As is the `size` attribute:
1062
1068
1063
1069
### File browser
1064
1070
1065
-
The file input is the most gnarly of the bunch and require additional JavaScript if you'd like to hook them up with functional *Choose file...* and selected file name text.
1071
+
The file input is the most gnarly of the bunch and requires additional JavaScript if you'd like to hook them up with functional *Choose file...* and selected file name text.
- We wrap the `<input>` in a `<label>` so the custom control properly triggers the file browser.
1077
-
- We hide the default file `<input>` via `opacity`.
1078
-
- We use `::after` to generate a custom background and directive (*Choose file...*).
1079
-
- We use `::before` to generate and position the *Browse* button.
1080
-
- We declare a `height` on the `<input>` for proper spacing for surrounding content.
1081
-
1082
-
In other words, it's an entirely custom element, all generated via CSS.
1080
+
We hide the default file `<input>` via `opacity` and instead style the `<label>`. The button is generated and positioned with `::after`. Lastly, we declare a `width` and `height` on the `<input>` for proper spacing for surrounding content.
Copy file name to clipboardExpand all lines: docs/4.0/migration.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,6 @@ While Beta 2 saw the bulk of our breaking changes during the beta phase, but we
35
35
36
36
- Sizing classes must be on the parent `.input-group` and not the individual form elements.
37
37
38
-
- Due to limitations in how CSS selectors work, all buttons must be the same element (e.g., `<a>` or `<button>`).
39
-
40
38
## Beta 2 changes
41
39
42
40
While in beta, we aim to have no breaking changes. However, things don't always go as planned. Below are the breaking changes to bear in mind when moving from Beta 1 to Beta 2.
0 commit comments