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
@@ -261,8 +261,9 @@ The [IgxAccordionComponent]({environment:angularApiUrl}/classes/igxaccordioncomp
261
261
- <kbd>Home</kbd> - navigates to the FIRST enabled panel in the accordion
262
262
- <kbd>End</kbd> - navigates to the LAST enabled panel in the accordion
263
263
264
-
## Angular Accordion Styling
265
-
The [accordion]({environment:angularApiUrl}/classes/igxaccordioncomponent.html) serves only as a container for the underlying [panels]({environment:angularApiUrl}/classes/igxexpansionpanelcomponent.html). Styles can be applied directly through the panel's theme, as described in the [styling section of the IgxExpansionPanel topic](expansion-panel.md#styling).
264
+
## Styling
265
+
266
+
The [`accordion`]({environment:angularApiUrl}/classes/igxaccordioncomponent.html) serves only as a container for the underlying [`panels`]({environment:angularApiUrl}/classes/igxexpansionpanelcomponent.html). Styles can be applied directly through the panel's theme, as described in the [`styling section of the IgxExpansionPanel topic`](expansion-panel.md#styling).
266
267
267
268
By design, there is a margin set to the expanded panels, in case that they are positioned within an `igx-accordion`. In order to modify it there is a property exposed inside the igx-expansion-panel theme.
268
269
In order to take advantage of the functions exposed by the theming engine, we have to import the `index` file in our style file:
@@ -274,33 +275,27 @@ In order to take advantage of the functions exposed by the theming engine, we ha
Following the simplest approach, we create a new theme that extends the [expansion-panel-theme]({environment:sassApiUrl}/index.html#function-expansion-panel-theme) and accepts an `$expanded-margin` parameter.
278
+
Following the simplest approach, we create a new theme that extends the [`expansion-panel-theme`]({environment:sassApiUrl}/index.html#function-expansion-panel-theme) and accepts an `$expanded-margin`, `$body-color` and `$header-focus-background` parameters.
278
279
```scss
279
280
$custom-panel-theme: expansion-panel-theme(
280
-
$expanded-margin:0px
281
+
$expanded-margin:10px,
282
+
$body-color:#282885,
283
+
$header-focus-background:#efefef
281
284
);
282
285
```
283
-
### Using CSS Variables
284
286
285
287
The last step is to include the component's theme.
286
288
```scss
287
-
:host {
288
-
@includecss-vars($custom-panel-theme);
289
-
}
289
+
@includecss-vars($custom-panel-theme);
290
290
```
291
291
292
-
### Using Theme Overrides
292
+
### Demo
293
293
294
-
In order to style components in Internet Explorer 11, we have to use a different approach, since CSS variables are not supported there.
If the component is using the [Emulated](themes/sass/component-themes.md#view-encapsulation)`ViewEncapsulation`, it is necessary to `penetrate` this encapsulation using `::ng-deep`. To prevent the custom theme from leaking into other components, make sure to wrap the `::ng-deep` in a `:host` selector:
The Ignite UI for Angular Action Strip component provides an overlay area containing one or more actions allowing additional UI and functionality to be shown on top of a specific target container upon user interaction e.g. hover. The container should be positioned relatively as the Action Strip attempts to overlay it and is itself positioned absolutely. Despite overlapped by an Action Strip, the main interactions and user access to the target container remain available.
## Getting Started with Ignite UI for Angular Action Strip
@@ -32,7 +29,7 @@ ng add igniteui-angular
32
29
33
30
For a complete introduction to the Ignite UI for Angular, read the [*getting started*](general/getting-started.md) topic.
34
31
35
-
The next step is to import the `IgxActionStripModule` in your **app.module.ts** file.
32
+
The next step is to import the `IgxActionStripModule` in your **app.module.ts** file.
36
33
37
34
```typescript
38
35
// app.module.ts
@@ -80,46 +77,46 @@ export class HomeComponent {}
80
77
Now that you have the Ignite UI for Angular Action Strip module or directives imported, you can start with a basic configuration of the `igx-action-strip` component.
81
78
82
79
## Using the Angular Action Strip Component
80
+
83
81
To initialize and position the Action Strip correctly, it needs to be inside a relatively positioned container:
By default, the Action Strip will be visible, but this can be configured via the [`hidden`]({environment:angularApiUrl}/classes/igxactionstripcomponent.html#hidden)@Input property.
96
94
97
95
### Menu look and feel
96
+
98
97
For scenarios where more than three action items will be shown, it is best to use [`IgxActionStripMenuItem`]({environment:angularApiUrl}/classes/igxactionstripmenuitemdirective.html) directive. Any item within the Action Strip marked with the `*igxActionStripMenuItem` structural directive will be shown in a dropdown, revealed upon toggling the more button i.e. the three dots representing the last action.
The same Action Strip instance can be used in multiple places in the document as long as the actions need not be visible simultaneously for them.
@@ -129,25 +126,25 @@ The best way to do so is via the [`show`]({environment:angularApiUrl}/classes/ig
129
126
> [!NOTE]
130
127
> The `show` API method uses [Angular Renderer2](https://angular.io/api/core/Renderer2) to append the Action Strip to that `element`.
131
128
132
-
133
129
## Usage in Grids
134
130
135
131
The Action Strip provides additional functionality and UI for the IgxGrid.
136
132
This can be utilized via grid action components and we are providing two default ones:
133
+
137
134
-[`IgxGridEditingActionsComponent`]({environment:angularApiUrl}/classes/igxgrideditingactionscomponent.html) - includes functionality and UI related to grid editing. It allows you to quickly toggle edit mode for cells or rows, depending on the value of the `rowEditable` option of the grid and whether deleting rows is allowed.
138
135
-[`IgxGridPinningActionsComponent`]({environment:angularApiUrl}/classes/igxgridpinningactionscomponent.html) - includes functionality and UI related to grid row pinning. It allows you to quickly pin rows and navigate between pinned rows and their disabled counterparts.
> These components inherit [`IgxGridActionsBaseDirective`]({environment:angularApiUrl}/classes/igxgridactionsbasedirective.html) and when creating a custom grid action component, it should also inherit `IgxGridActionsBaseDirective`.
153
150
@@ -165,52 +162,42 @@ This can be utilized via grid action components and we are providing two default
165
162
## Styling
166
163
167
164
To customize the Action Strip, you first need to import the `index` file, where all styling functions and mixins are located.
165
+
168
166
```scss
169
167
@use"igniteui-angular/theming"as*;
170
168
171
169
// IMPORTANT: Prior to Ignite UI for Angular version 13 use:
Copy file name to clipboardExpand all lines: en/components/autocomplete.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,6 @@ Angular Autocomplete is a search box directive that enables users to easily find
11
11
12
12
The [`igxAutocomplete`]({environment:angularApiUrl}/classes/igxautocompletedirective.html) directive provides a way to enhance a text input by showing an [`igxDropDown`]({environment:angularApiUrl}/classes/igxdropdowncomponent.html) with suggested options, provided by the developer. The suggestions will show once you start typing in the text input or use the `Arrow Up`/`Arrow Down` keys.
13
13
</p>
14
-
<divclass="divider"></div>
15
14
16
15
## Angular Autocomplete Example
17
16
@@ -256,7 +255,7 @@ The `drop-down` component, used as provider for suggestions, will expose the fol
256
255
## Styling
257
256
Every component has its own theme.
258
257
259
-
To get the `igxAutocomplete` styled, you have style its containing components. In our case, we need to use both the [input-group-theme]({environment:sassApiUrl}/index.html#function-input-group-theme) and the [drop-down-theme]({environment:sassApiUrl}/index.html#function-drop-down-theme).
258
+
To get the `igxAutocomplete` styled, you have to style its containing components. In our case, these are the [input-group-theme]({environment:sassApiUrl}/index.html#function-input-group-theme) and the [drop-down-theme]({environment:sassApiUrl}/index.html#function-drop-down-theme).
260
259
261
260
Take a look at the [`igxInputGroup`](input-group.md#styling) and the [`igxDropdown`](drop-down.md#styling) styling sections to get a better understanding of how to style those two components.
In order to style components for Internet Explorer 11 and older browsers, we have to use different approach, since it doesn't support CSS variables.
186
-
187
-
If the component is using an [`Emulated`](themes/sass/component-themes.md#view-encapsulation) ViewEncapsulation, it is necessary to `penetrate` this encapsulation using `::ng-deep`. On the other side, in order to prevent the custom theme to leak to other components, be sure to include the `:host` selector before `::ng-deep`:
188
-
189
-
```scss
190
-
:host {
191
-
::ng-deep {
192
-
// Pass the custom avatar theme to the `igx-avatar` mixin
193
-
.initials-avatar {
194
-
@include avatar($custom-avatar-theme);
195
-
}
196
-
}
176
+
.initials {
177
+
@includecss-vars($custom-avatar-theme);
197
178
}
198
179
```
199
180
@@ -233,7 +214,7 @@ You can also use one of the predefined sizes, assigning it to the `--ig-size` va
0 commit comments