[next/Breaking Change] Make Markdown's newline handling compatible with browsers' behavior #16805
Conversation
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
5 tasks
tats-u
force-pushed
the
markdown-newline-handling
branch
from
efda8c7 to
4376cfd
Compare
tats-u
force-pushed
the
markdown-newline-handling
branch
from
4376cfd to
e8c10f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
A part of #15081
Fixes #14936
Blocked by #16816(Merged)Always convert
\nbetween han (including Japanese kana) and non-han to a space and allow line breaking at a space between han and non-han again (banned by #16691)I'll rebase this to
nextafternextmergesmainone more time.nextdoesn't include the change by #16691 and this PR depends on it.Question
Checklist
docs/directory).changelog_unreleased/*/XXXX.mdfile followingchangelog_unreleased/TEMPLATE.md.✨Try the playground for this PR✨