FAQ
Here are the frequently asked questions about Ant Design and Blazor that you should look up before you ask in the community or create a new issue. We also maintain a FAQ issues label for common github issues.
If your question is style-related, please refer to the list of frequently asked questions about Ant Design React。
Select Dropdown DatePicker TimePicker Popover Popconfirm disappears when I click another popup component inside it. How do I resolve this?
This is related to the scrolling area of the overlay, which by default only scrolls with the body.
Use <Select PopupContainerSelector="#some-scroll-area"> (API Documentation) to render the component into the scroll area ( where #some-scroll-area is the CSS Selector of the scrolling element).
And make sure that #some-scroll-area element is position: relative or position: absolute.
How do I modify the default theme of Ant Design?
See: https://ant.design/docs/react/customize-theme
How do I add HTML attributes such as data-testid or aria-describedby?
DOM components inherit the AdditionalAttributes catch-all parameter from AntDomComponentBase. You can pass unmatched attributes directly or supply an IReadOnlyDictionary<string, object> through AdditionalAttributes. The dictionary type is the same as the existing input API.
<Button data-testid="save-button" data-action="save" aria-describedby="save-help"
form="editor" name="action" value="save">
Save
</Button>
<span id="save-help">Saves your current changes.</span>
Attributes are updated or removed on the next render when the dictionary changes or is cleared. Boolean values follow Blazor HTML rendering rules: true adds a boolean attribute and false/null removes it. Use strings such as "false" for ARIA values.
| Component | Attribute target |
|---|---|
Button, DownloadButton, Switch |
Native button |
Input, InputNumber, Checkbox, Radio, SegmentedItem |
Native input, including when surrounded by wrappers |
TextArea, Mentions |
Native textarea |
DatePicker, including time picker mode |
Editable input |
RangePicker |
Both editable inputs; avoid attributes that must be unique, such as id |
Select, TreeSelect, Cascader |
Search/combobox input in either single or multiple mode |
AutoComplete |
Default input; when supplying ChildContent, attach attributes to your custom input |
Image, MenuLink, Form |
img, a, and form, respectively |
TabPane, RateItem |
Element with role="tab" or role="radio" |
Modal, Confirm |
Dialog element with role="document" |
Column, ActionColumn, Selection, SummaryCell |
Rendered header/body cells; no forwarding to measurement or placeholder cells |
Table, Slider, groups, layout, typography, and other ordinary DOM components |
Outermost component element (for Table, the wrapper rather than each table/cell) |
Tooltip, Popover, Popconfirm, Dropdown |
Trigger wrapper, when present; with Unbound/external trigger references, attach attributes to the supplied trigger |
Message, Notification |
Each rendered placement container |
Dedicated parameters and component-managed attributes win collisions. Set Class, Style, Id, Disabled, AriaLabel, etc. through their parameters; dictionary entries do not replace generated classes, managed ARIA state, or internal event handlers. Use component callbacks such as OnClick for managed events. Additional event attributes are accepted where the component has no handler for that event. Existing named dictionaries (Attributes, UnmatchedAttributes, OnCell, OnHeaderCell, and row attributes) remain supported; their entries take precedence over the shared dictionary for collisions. Existing behavior within these legacy dictionaries is retained.
AntComponentBase itself has no attribute contract. Providers, templates, service containers (AntContainer, modal/drawer/message host containers, image preview containers), and other components without their own DOM element do not forward attributes. Mentions.TextareaTemplate also owns its markup: attach attributes inside the template. Custom components derived from AntDomComponentBase must explicitly forward AdditionalAttributes to their chosen element, placing Razor @attributes before managed attributes. With RenderTreeBuilder, call AddMultipleAttributes before adding managed attributes.
Why does modifying props in mutable way not trigger a component update?
Blazor use shallow compare of props to optimize performance. You should always pass the new object when updating the state. Please ref React's document
Components are not vertically aligned when placed in single row.
Try Space component to make them aligned.
antd doesn't work well in mobile.
antd is not designed for mobile. There is also no Blazor implementation of AntDesign Mobile in development, so if you are interested in contributing code, please contact us.
Do you guys have any channel or website for submitting monetary donations, like through PayPal or Alipay?
https://opencollective.com/ant-design-blazor
Why is CSS isolation not working for Ant Design Blazor components
Blazor applies scope attributes only to native HTML elements to enable CSS isolation. Official documentation
This does not include AntDesign Blazor components, thus these components need to be wrapped in a native HTML element to support CSS isolation.
As you can see, the <div> is enclosing the <Layout Class="layout"> which is an AntDesign Blazor component.
@page "/test" <--- Blazor
<div> <--- HTML
<Layout Class="layout"> <--- AntDesign
[...]
More explanation in Zonciu´s comment
Now you can create a ".razor.css" file for that page and add your CSS for the "layout" class of the Layout AntDesign component.
::deep .layout {
background: #fff;
}
The ::deep prefix has to be used on all the CSS for AntDesign Blazor components using CSS isolation.
If you get warnings like "::deep is not a valid pseudo-element." then you can ignore these. See the documentation
Errors and Warnings
Here are some errors & warnings that you may encounter while using AntDesign Blazor, although most of these are not actual bugs of antd itself.
When binding events of components, a compilation error occurs: CS1503 cannot convert from 'method group' to 'Microsoft.AspNetCore.Components.EventCallback'
This is because the component is generic, and it is necessary to explicitly set the generic type parameters of the component (starting with "T").
<Select TItem="string"
TItemValue="string"
DataSource="@_personNames"
OnSelectedItemChanged="@((personName) => {...}))">
</Select>
Build error for Col components
Since the Col component is recognised by VS as a col element, you can use AntDesign.Col to avoid error.
Naming conflicts between the Column in the Form component and the Column in AntDesign Charts
It is also possible to use the namespace AntDesign.Column or AntDesign.Charts.Column to avoid error.