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
Copy file name to clipboardExpand all lines: website/docs/components/app-side-nav/partials/code/how-to-use.md
+4-6
Original file line number
Diff line number
Diff line change
@@ -201,18 +201,16 @@ Each one of these states has CSS class names associated, and they’re used by t
201
201
202
202
The App Side Nav component **automatically**:
203
203
204
-
- fades in/out the “actions” block in the header and the content injected in the body via “portals”.
204
+
- fades in/out the the content in the navigation
205
205
- swaps the toggle button icon from “menu” to “close” and moves it from one position to another
206
206
207
-
Any other content in the App Side Nav needs to be **explicitly handled** by the consumers (in this way they have full control of the content they add, and they can customize the transition as they want/need).
208
-
209
-
One possible way to do it is to use the **`hds-app-side-nav--hide-when-minimized` class**. This is a special class that can be applied to a DOM element so that it **automatically** fades in/out when the App Side Nav changes its “minimization” state.
210
-
211
-
More specifically:
207
+
More specifically, the animation is:
212
208
213
209
-`minimized → maximized` transition: the content appears with a fade-in effect, when the width animation is already completed (the width is maximized)
214
210
-`maximized → minimized` transition: the content disappears at once with no transition, before the width animation starts
215
211
212
+
Any other content in the App Side Nav needs to be **explicitly handled** by the consumers (in this way they have full control of the content they add, and they can customize the transition as they want/need).
213
+
216
214
#### Advanced customization
217
215
218
216
Some aspects of the responsiveness/animation/transition of the App Side Nav are parameterized in code via CSS custom properties. It means that _in theory_ they could be customized/overwritten. This though is **something that we don’t recommend**.
0 commit comments