Merged
Conversation
JiuqingSong
requested review from
BryanValverdeU,
flyingbee2012,
ianeli1,
juliaroldi and
vinguyen12
juliaroldi
approved these changes
Mar 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bug 415232: [In-app issue] Bulleted items in compose will randomly shift
When reuse list element, we need to apply list metadata to list element to force it has a correct list type, so that the next list item can reuse the same list element. Howerver, if this is a deeper level list item, on the upper level today we are retrieving format for a wrong list level, because we are checking context.listFormat.nodeStack.length, this can have larger value than current list value.
To solve this, add a new property for list format in context, use it to pass in the current list level, so metadata applier can know the correct list level.