From dc14080f222501bec203b0baeb6c278ca59a20aa Mon Sep 17 00:00:00 2001 From: "U-CPHDOMAIN\\dtr" Date: Wed, 10 Jul 2024 18:46:07 -0400 Subject: [PATCH] Updating understanding/20/resize-text.html --- understanding/20/resize-text.html | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/understanding/20/resize-text.html b/understanding/20/resize-text.html index 899450df9f..b74c47132e 100644 --- a/understanding/20/resize-text.html +++ b/understanding/20/resize-text.html @@ -56,10 +56,12 @@

Intent of Resize Text

cell content that is too long to be displayed in a column can be truncated, and the full content of the cell is available to the user when the cell receives focus. The content of a user interface component may also become too wide in user interfaces - where the user can resize the column width. In this type of user interface component, - line wrapping is not required; truncation is acceptable if the component's full content - is available on focus or after user activation and an indication that this information - can be accessed, is provided to the user in some way besides the fact that it is truncated. + where the user can resize the column width. Alternately, there might not be any + user-supplied content or user-specified column width - there might simply not be enough + space for the content. In these cases, line wrapping is not required; truncation is + acceptable if the component's full content is available on focus or after user activation + and an indication that this information can be accessed, is provided to the user in some + way besides the fact that it is truncated.

Content satisfies the Success Criterion if it can be scaled up to 200%, that is, up