Skip to content

Commit dc22e11

Browse files
committed
chore(TileLayout): update article
1 parent 3ca6de8 commit dc22e11

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

knowledge-base/tilelayout-kb-nested-instances.md renamed to knowledge-base/tilelayout-nested-instances.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -31,13 +31,18 @@ This KB article answers the following questions:
3131

3232
## Solution
3333

34-
When using two nested [TileLayout](https://docs.telerik.com/blazor-ui/components/tilelayout/overview) components in a Blazor application, resizing or reordering the child component expectedly affect the parent component. This behavior occurs because the resize and reorder events propagate through both levels of TileLayout components.
34+
When using two nested [TileLayout](https://docs.telerik.com/blazor-ui/components/tilelayout/overview) components in a Blazor application, resizing or reordering the child component expectedly affects the parent component. This behavior occurs because the resize and reorder events propagate through both levels of TileLayout components.
3535

36-
Nesting TileLayouts is uncommon, but generally possible if tile resizing and reordering are enabled only for one level at a time. It is important to clarify that with the users, so do not expect they can drag tiles across component instances, which is not possible.
36+
Nesting TileLayouts is uncommon, but generally possible if the resizing and reordering are enabled only for one level at a time. It is important to clarify that with the users, so they do not expect they can drag tiles across component instances, which is not possible.
3737

38-
To manage nested TileLayout components without unwanted resize and reorder behaviors, enable resizing and reordering only for the innermost TileLayout instance. This approach prevents event propagation issues and enhances user experience by providing a clear and manageable interaction model for nested components.
38+
To manage nested TileLyouts with resizing and reordering:
3939

40-
>caption Enable resize and reorder for onle level of nested tiles
40+
1. Bind the `Resizable` and `Reorderable` of both TileLayout instances to different variables, so you can toggle them during runtime.
41+
1. Choose your preferred UI to allow the user enable the resizing and reordering of the specific level of tiles. The example below uses ToggleButtons.
42+
1. Once the user enables the resizing and reordering for one level, programmatically disable the features for the other level.
43+
1. (Optional) Use CSS to manage the overflow of the parent TileLayout. This will prevent the parent TileLayout from expanding if the user resizes the tiles in the child TileLayout.
44+
45+
>caption Enable resize and reorder for only level of nested TileLayouts
4146
4247
````CSHTML
4348
<style>
@@ -155,6 +160,6 @@ To manage nested TileLayout components without unwanted resize and reorder behav
155160
````
156161

157162
## See Also
158-
- [TileLayout Overview](https://docs.telerik.com/blazor-ui/components/tilelayout/overview)
159-
- [TileLayout Resizable Documentation](https://docs.telerik.com/blazor-ui/components/tilelayout/features#resizable)
160-
- [TileLayout Reorderable Documentation](https://docs.telerik.com/blazor-ui/components/tilelayout/features#reorderable)
163+
- [TileLayout Overview]({%slug tilelayout-overview%})
164+
- [TileLayout Reorderable Documentation]({%slug tilelayout-reorder%})
165+
- [TileLayout Resizable Documentation]({%slug tilelayout-resize%})

0 commit comments

Comments
 (0)