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: docs/migration/wsc55/icons.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,6 +148,15 @@ This can be replaced using a proper button element which also provides proper ac
148
148
</li>
149
149
```
150
150
151
+
### Replacing Icons in CSS
152
+
153
+
Icons created through CSS properties are generally not supported.
154
+
It was often used as a convenient way to introduce a new icon with little hassle, but has way too many downsides, including but not limited to accessibility.
155
+
156
+
Existing icons injected through CSS properties are dysfunctional and must be converted into regular icons that are injected into the DOM.
157
+
If you cannot embed them directly in the template, you should inject those using JavaScript on runtime.
158
+
It is possible to inject icons using JavaScript on page load by relying entierly on native JavaScript, because the icon component is eagerly loaded ahead of time, preventing any flicker or layout shifts.
159
+
151
160
### Migrating Admin-Configurable Icons
152
161
153
162
If admin-configurable icon names (e.g. created by [`IconFormField`](../../php/api/form_builder/form_fields.md#iconformfield)) are stored within the database, these need to be migrated with an [upgrade script](../../package/pip/script.md).
0 commit comments