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: Document-Processing/Excel/Spreadsheet/Blazor/cell-range.md
+106Lines changed: 106 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,6 +102,112 @@ The following illustration demonstrates the use of autofill in the Spreadsheet c
102
102
103
103
104
104
105
+
## Events
106
+
107
+
The Blazor Spreadsheet provides events that are triggered during autofill operations, such as [AutofillActionBegin](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Spreadsheet.AutofillActionBeginEventArgs.html) and [AutofillActionEnd](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Spreadsheet.AutofillActionEndEventArgs.html). These events enable the execution of custom actions before and after an autofill operation, allowing for validation, customization, and response handling.
108
+
109
+
### AutofillActionBegin
110
+
111
+
The `AutofillActionBegin` event is triggered before an autofill operation is performed. This event provides an opportunity to validate the autofill operation and apply restrictions based on custom logic, such as preventing the operation under specific conditions.
112
+
113
+
**Purpose**
114
+
115
+
This event is useful for scenarios where autofill behavior needs to be controlled dynamically—such as restricting autofill in specific ranges or preventing autofill based on certain conditions.
116
+
117
+
**Event Arguments**
118
+
119
+
The event uses the [AutofillActionBeginEventArgs](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Spreadsheet.AutofillActionBeginEventArgs.html) class, which includes the following properties:
120
+
121
+
| Event Arguments | Description |
122
+
|----------------|-------------|
123
+
| FillRange (read-only) | The address of the target range for the autofill operation (e.g., "Sheet1!A2:A5"). |
124
+
| DataRange (read-only) | The source data range for the autofill operation (e.g., "Sheet1!A1:A1"). |
125
+
| Direction (read-only) | The direction of the autofill operation ("Down", "Right", "Up", or "Left"). |
126
+
| Cancel | A boolean value to cancel the autofill operation. |
public void OnAutofillActionBegin(AutofillActionBeginEventArgs args)
147
+
{
148
+
// Prevent autofill for a specific range.
149
+
if (args.FillRange == "A1:A10")
150
+
{
151
+
args.Cancel = true;
152
+
}
153
+
154
+
// Prevent autofill when dragging upward.
155
+
if (args.Direction == "Up")
156
+
{
157
+
args.Cancel = true;
158
+
}
159
+
}
160
+
}
161
+
162
+
{% endhighlight %}
163
+
{% endtabs %}
164
+
165
+
**AutofillActionEnd**
166
+
167
+
The `AutofillActionEnd` event is triggered after an autofill operation has been successfully completed. This event provides detailed information about the completed autofill action, enabling further processing or logging if required.
168
+
169
+
**Purpose**
170
+
171
+
This event is useful for scenarios where post-autofill actions are needed, such as logging the autofill operation, updating related data, or triggering additional UI updates.
172
+
173
+
**Event Arguments**
174
+
175
+
The event uses the [AutofillActionEndEventArgs](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.Spreadsheet.AutofillActionEndEventArgs.html) class, which includes the following properties:
176
+
177
+
| Event Arguments | Description |
178
+
|----------------|-------------|
179
+
| FillRange (read-only) | The address of the target range where the autofill was applied (e.g., "Sheet1!A2:A5"). |
180
+
| DataRange (read-only) | The source data range used for the autofill operation (e.g., "Sheet1!A1:A1"). |
181
+
| Direction (read-only) | The direction of the autofill operation ("Down", "Right", "Up", or "Left"). |
public void OnAutofillActionEnd(AutofillActionEndEventArgs args)
202
+
{
203
+
// Log or process the completed autofill operation.
204
+
Console.WriteLine($"Autofill completed for range: {args.FillRange}");
205
+
}
206
+
}
207
+
208
+
{% endhighlight %}
209
+
{% endtabs %}
210
+
105
211
## Clear
106
212
107
213
Clear support helps clear the cell contents (formulas and data) and formats (including number formats) in a Spreadsheet. When **Clear All** is applied, both the contents and the formats will be cleared simultaneously.
Copy file name to clipboardExpand all lines: Document-Processing/PDF/PDF-Viewer/blazor/accessibility.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ documentation: ug
8
8
---
9
9
10
10
# Accessibility in Syncfusion® Blazor SfPdfViewer
11
-
The Blazor SfPdfViewer component followed the accessibility guidelines and standards, including [ADA](https://www.ada.gov/), [Section 508](https://www.section508.gov/), [WCAG 2.2](https://www.w3.org/TR/WCAG22/) standards, and [WCAG roles](https://www.w3.org/TR/wai-aria/#roles) that are commonly used to evaluate accessibility.
11
+
The Blazor SfPdfViewer component follows established accessibility guidelines and standards, including the [ADA](https://www.ada.gov/), [Section 508](https://www.section508.gov/), [WCAG 2.2](https://www.w3.org/TR/WCAG22/) standards, and [WCAG roles](https://www.w3.org/TR/wai-aria/#roles), which are commonly used to evaluate accessibility.
12
12
13
13
The accessibility compliance for the Blazor SfPdfViewer component is outlined below.
14
14
@@ -37,7 +37,7 @@ The accessibility compliance for the Blazor SfPdfViewer component is outlined be
37
37
38
38
## WAI-ARIA attributes
39
39
40
-
[WAI-ARIA](https://www.w3.org/WAI/ARIA/apg/patterns/alert/) (Accessibility Initiative – Accessible Rich Internet Applications) defines a way to increase the accessibility of web pages, dynamic content, and user interface components developed with Ajax, HTML, JavaScript,and related technologies. ARIA provides additional semantics to describe the role, state, and functionality of web components. The following ARIA attributes are used in the Blazor SfPdfViewer component:
40
+
[WAI-ARIA](https://www.w3.org/WAI/ARIA/apg/patterns/alert/) (Accessibility Initiative – Accessible Rich Internet Applications) defines a way to enhance the accessibility of web pages, dynamic content, and user interface components developed with Ajax, HTML, JavaScript,and related technologies. ARIA provides additional semantics to describe the role, state, and functionality of web components. The following ARIA attributes are used in the Blazor SfPdfViewer component:
41
41
42
42
| Attributes | Purpose |
43
43
| --- | --- |
@@ -57,46 +57,46 @@ The accessibility compliance for the Blazor SfPdfViewer component is outlined be
57
57
58
58
## Keyboard interaction
59
59
60
-
The Blazor SfPdfViewer component followed the [keyboard interaction](https://www.w3.org/WAI/ARIA/apg/patterns/alert/#keyboardinteraction) guideline, making it easy for people who use assistive technologies (AT) and those who completely rely on keyboard navigation. The following keyboard shortcuts are supported by the Message component.
60
+
The Blazor SfPdfViewer component follows the [keyboard interaction](https://www.w3.org/WAI/ARIA/apg/patterns/alert/#keyboardinteraction) guideline, making it accessible to users who rely on assistive technologies (AT) and keyboard navigation. The following keyboard shortcuts are supported by the SfPdfViewer component.
61
61
62
62
| Windows | Mac | Actions |
63
63
| --- | --- | --- |
64
64
|||**Shortcuts for page navigation**|
65
-
| <kbd>Ctrl</kbd> + <kbd>←</kbd> / <kbd>Ctrl</</kbd> + <kbd>↑</kbd> | <kbd>⌘</kbd> + <kbd>←</kbd> or <kbd>⌘</kbd> + <kbd>↑</kbd> |Navigate to the first page |
66
-
| <kbd>Ctrl</kbd> + <kbd>→</kbd> / <kbd>Ctrl</</kbd> + <kbd>↓</kbd> | <kbd>⌘</kbd> + <kbd>→</kbd> or <kbd>⌘</kbd> + <kbd>↓</kbd> |Navigate to the last page |
65
+
| <kbd>Ctrl</kbd> + <kbd>←</kbd> / <kbd>Ctrl</kbd> + <kbd>↑</kbd> | <kbd>⌘</kbd> + <kbd>←</kbd> / <kbd>⌘</kbd> + <kbd>↑</kbd> |Navigate to the first page |
66
+
| <kbd>Ctrl</kbd> + <kbd>→</kbd> / <kbd>Ctrl</kbd> + <kbd>↓</kbd> | <kbd>⌘</kbd> + <kbd>→</kbd> / <kbd>⌘</kbd> + <kbd>↓</kbd> |Navigate to the last page |
67
67
| <kbd>←</kbd> | <kbd>←</kbd> / <kbd>⇧</kbd> + <kbd>Space</kbd> |Navigate to the previous page |
68
68
| <kbd>→</kbd> | <kbd>→</kbd> / <kbd>Space</kbd> | Navigate to the next page |
69
69
| <kbd>Ctrl</kbd> + <kbd>G</kbd> | <kbd>⌘</kbd> + <kbd>G</kbd> | Go To The Page|
The Blazor SfPdfViewer component's accessibility levels are ensured through an [axe-core](https://www.nuget.org/packages/Deque.AxeCore.Playwright) with playwright tests.
98
98
99
-
The accessibility compliance of the Blazor SfPdfViewer component is shown in the following sample. Open the [sample](https://blazor.syncfusion.com/accessibility/pdfviewer) in a new window to evaluate the accessibility of the Blazor SfPdfViewer component with accessibility tools.
99
+
The accessibility compliance of the Blazor SfPdfViewer component is demonstrated in the following sample. Open the [SfPdfViewer accessibility sample](https://blazor.syncfusion.com/accessibility/sfpdfviewer) in a new window to evaluate the accessibility of the Blazor SfPdfViewer component with accessibility tools.
0 commit comments