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
The following section describes behavior introduced in<strong>v11.7</strong>: the updated <code>error</code> type and the required asterisk feature. If you are viewing the v11.6 version, <Link href={window.location.pathname.match(/v\d+_\d+/) ?window.location.pathname.replace(/v\d+_\d+/, 'v11_7') :`/v11_7${window.location.pathname}`}>switch to v11.7</Link> to see these features working correctly.
80
+
</Alert>
81
+
```
82
+
74
83
The `error` type has been updated to meet accessibility requirements with proper icons and visual styling. Previously, there was a `newError` type that provided this enhanced behavior, but it has been consolidated into the standard `error` type for consistency. `newError` has been deprecated.
75
84
76
85
We also introduced the "required asterisk" which displays an `*` character next to field labels that are required. This update applies to **all** InstUI form components, so if you were relying on a custom solution for this feature before, you need to remove that to avoid having double asterisks.
Copy file name to clipboardExpand all lines: docs/theming/legacy-theme-overrides.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
@@ -7,6 +7,15 @@ relevantForAI: true
7
7
8
8
## Using theme overrides
9
9
10
+
```js
11
+
---
12
+
type: embed
13
+
---
14
+
<Alert variant="warning" margin="0 0 medium">
15
+
The examples on this page use the <strong>legacy theming system</strong> and are designed for<strong>v11.6</strong>components. If you are viewing the v11.7 version, <Link href={window.location.pathname.match(/v\d+_\d+/) ?window.location.pathname.replace(/v\d+_\d+/, 'v11_6') :`/v11_6${window.location.pathname}`}>switch to v11.6</Link> to see the examples working correctly.
16
+
</Alert>
17
+
```
18
+
10
19
This document gives an overview on how you can customize Instructure UI components by tweaking their theme variables.
11
20
While this gives you a level of flexibility on the look and feel of the components you should be aware of 2 things:
Copy file name to clipboardExpand all lines: docs/theming/new-theme-overrides.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,21 @@
1
1
---
2
-
title: New Theme Overrides
2
+
title: New theme overrides
3
3
category: Theming
4
4
order: 6
5
5
relevantForAI: true
6
6
---
7
7
8
8
## New Theme Override Patterns
9
9
10
+
```js
11
+
---
12
+
type: embed
13
+
---
14
+
<Alert variant="warning" margin="0 0 medium">
15
+
The examples on this page use the <strong>newtheming system</strong> and require <strong>v11.7+</strong>components. If you are viewing the v11.6 version, <Link href={window.location.pathname.match(/v\d+_\d+/) ?window.location.pathname.replace(/v\d+_\d+/, 'v11_7') :`/v11_7${window.location.pathname}`}>switch to v11.7</Link> to see the examples working correctly.
16
+
</Alert>
17
+
```
18
+
10
19
This guide covers all the override patterns available in the new theming system (v11.7+). The new system uses a layered token architecture: **primitives** (raw values) -> **semantics** (meaning) -> **components** (per-component tokens).
11
20
12
21
Overrides are applied via the `themeOverride` prop on `InstUISettingsProvider`, which is separate from the `theme` prop. The `theme` prop replaces the active theme entirely; `themeOverride` layers modifications on top.
Copy file name to clipboardExpand all lines: docs/upgrading/upgrade-guide.md
+83-83Lines changed: 83 additions & 83 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Upgrade Guide for multi version (beta)
2
+
title: Upgrade Guide for multi version
3
3
category: Upgrading
4
4
order: 9999999
5
5
---
@@ -72,23 +72,6 @@ type: embed
72
72
73
73
```
74
74
75
-
### Billboard
76
-
77
-
```js
78
-
---
79
-
type: embed
80
-
---
81
-
<V12ChangelogTable
82
-
removed={[
83
-
{name:"iconHoverColorInverse",note:""},
84
-
{name:"iconHoverColor",note:""},
85
-
{name:"iconColor",note:""},
86
-
{name:"messageColorInverse",note:""}
87
-
]}
88
-
/>
89
-
90
-
```
91
-
92
75
### BaseButton
93
76
94
77
All button components (Button, IconButton, CondensedButton) share BaseButton's theme tokens.
@@ -229,20 +212,18 @@ type: embed
229
212
230
213
```
231
214
232
-
### CloseButton
233
-
234
-
CloseButton no longer has its own dedicated theme tokens in v2. Offset spacing now uses `sharedTokens.spacing`, and visual styling comes from BaseButton tokens.
CloseButton no longer has its own dedicated theme tokens in v2. Offset spacing now uses `sharedTokens.spacing`, and visual styling comes from BaseButton tokens.
Drilldown itself has no token changes. However, its sub-components share tokens with Options components, so the token changes listed under Options apply here as well:
@@ -1164,40 +1164,40 @@ type: embed
1164
1164
1165
1165
```
1166
1166
1167
-
### Rating
1167
+
### RangeInput
1168
+
1169
+
-`thumbVariant` prop has been removed. The component now always renders the previously-`accessible` thumb (better color contrast, border, and inset focus ring).
{oldName:"valueSmallPadding",newName:"valueSmallPadding",note:"now only sets horizontal padding of the value"},
1183
+
{oldName:"valueMediumPadding",newName:"valueMediumPadding",note:"now only sets horizontal padding of the value"},
1184
+
{oldName:"valueLargePadding",newName:"valueLargePadding",note:"now only sets horizontal padding of the value"}
1178
1185
]}
1179
1186
/>
1180
1187
1181
1188
```
1182
1189
1183
-
### RangeInput
1184
-
1185
-
-`thumbVariant` prop has been removed. The component now always renders the previously-`accessible` thumb (better color contrast, border, and inset focus ring).
0 commit comments