Don't include extra linebreak positions after an explicit break. #1003
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.
This PR fixes a problem with CHTML output where in-line expressions with explicit line breaks could end up with extra vertical space at the explicit break if the part after it starts with an operator and is too wide for the container. To do with, we mark the nodes with explicit linebreaks, and if we are just after an explicit line break, we don't mark an operator as breakable (preventing an extra line break from occurring right after an explicit one). In the CHTML output, we don't insert breakpoints before explicit linebreaks (preventing an extra line break from occurring before that).
A test case is to use
to see that there are no extra blank lines in CHTML output.