Skip to content

Commit 7198d8b

Browse files
DOC-3132: Not specifying a notification type (or specifying incorrect one) now defaults to 'info' (#3622)
* DOC-3132: Not specifying a notification type (or specifying incorrect one) now defaults to 'info'. * Update modules/ROOT/pages/7.7.0-release-notes.adoc Co-authored-by: Karl Kemister-Sheppard <[email protected]> --------- Co-authored-by: Karl Kemister-Sheppard <[email protected]>
1 parent 54ca317 commit 7198d8b

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

modules/ROOT/pages/7.7.0-release-notes.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -205,6 +205,13 @@ For information on the **Accessibility Checker** plugin, see: xref:a11ychecker.a
205205

206206
{productname} {release-version} also includes the following improvements:
207207

208+
=== Not specifying a notification type (or specifying an incorrect one) now defaults to 'info'.
209+
// #TINY-11661
210+
211+
In earlier versions of {productname}, an undefined or incorrect `type` property in the notification manager resulted in irregular notifications with no background and a placeholder icon, making them difficult to read.
212+
213+
With the release of {productname} {release-version}, this behavior has been improved. The `type` property now defaults to `info` when an invalid or missing value is detected, resulting in a proper looking notification that is easy to understand.
214+
208215
=== Extended the `forceReadOnly` functionality to support the new `disabled` option in addition to readonly mode.
209216
// #TINY-11490
210217

0 commit comments

Comments
 (0)