From 460bea4024dba391621968647b839b7bf68211e5 Mon Sep 17 00:00:00 2001 From: Val Lorentz Date: Tue, 4 Oct 2022 05:31:10 +0200 Subject: [PATCH] Fix definition of `data-mx-color` values (#1260) * Fix definition of `data-mx-color` values * Create 1260.clarification * Update changelogs/client_server/newsfragments/1260.clarification Co-authored-by: Travis Ralston Co-authored-by: Travis Ralston --- changelogs/client_server/newsfragments/1260.clarification | 1 + content/client-server-api/modules/instant_messaging.md | 5 +++-- 2 files changed, 4 insertions(+), 2 deletions(-) create mode 100644 changelogs/client_server/newsfragments/1260.clarification diff --git a/changelogs/client_server/newsfragments/1260.clarification b/changelogs/client_server/newsfragments/1260.clarification new file mode 100644 index 00000000..3ccb2333 --- /dev/null +++ b/changelogs/client_server/newsfragments/1260.clarification @@ -0,0 +1 @@ +Fix various typos throughout the specification. diff --git a/content/client-server-api/modules/instant_messaging.md b/content/client-server-api/modules/instant_messaging.md index 7f9b3ca1..47440cd3 100644 --- a/content/client-server-api/modules/instant_messaging.md +++ b/content/client-server-api/modules/instant_messaging.md @@ -47,8 +47,9 @@ Not all attributes on those tags should be permitted as they may be avenues for other disruption attempts, such as adding `onclick` handlers or excessively large text. Clients should only permit the attributes listed for the tags below. Where `data-mx-bg-color` and `data-mx-color` -are listed, clients should translate the value (a 6-character hex color -code) to the appropriate CSS/attributes for the tag. +are listed, clients should translate the value (a `#` character followed +by a 6-character hex color code) to the appropriate CSS/attributes for +the tag. `font` `data-mx-bg-color`, `data-mx-color`, `color`