Repository navigation
fix(web): long screen-reader announcements keep emoji whole at the cutoff #35681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+26
−6
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
4268869
test(web): screen-reader announcement cutoffs keep emoji whole
juliusmarminge fe6b1a4
fix(web): long screen-reader announcements keep emoji whole at the cu…
juliusmarminge 1106e27
Merge remote-tracking branch 'origin/main' into factory/issue-35670
juliusmarminge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Avoid building a full code-point array for long messages.
cutTextcallsArray.from(text)on the full message whenever the message is over the limit. The function keeps only the first 2,000 code points, so this allocates one entry per code point of the entire message. Assistant responses can be long, so a very large message can cause a noticeable client pause.Suggested fix
Iterate over the string with
for...ofand stop aftermaxLength + 1code points. Returnnullwhen the text has no more thanmaxLengthcode points. Otherwise, return the firstmaxLengthcode points. This keeps the current return contract and avoids the full-array allocation.