Skip to content
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.

Sign up for GitHub

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

Jump to bottom

0.6.1 -> 0.6.2 broke breaks option (Regression) #1505

Closed
fdietze opened this issue Jun 28, 2019 · 3 comments · Fixed by #1507
Closed

0.6.1 -> 0.6.2 broke breaks option (Regression) #1505

fdietze opened this issue Jun 28, 2019 · 3 comments · Fixed by #1507
Assignees
@UziTech
Labels
L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue

Comments

@fdietze
Copy link

fdietze commented Jun 28, 2019

Describe the bug
After updating from 0.6.1 to 0.6.2, I noticed that my linebreaks got lost.

To Reproduce
0.6.1 with option breaks enabled:

A
B

output:

<p>A<br>B</p>

(which is correct)

with 0.6.2 it becomes:

<p>A
B</p>
@UziTech
Copy link
Member

UziTech commented Jun 28, 2019

confirmed:

v0.6.2 demo
v0.6.1 demo

@UziTech UziTech added the L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue label Jun 28, 2019
@UziTech
Copy link
Member

UziTech commented Jun 28, 2019

looks like it is #1460 that broke this. I will try to find a solution for both to work.

@UziTech UziTech self-assigned this Jun 28, 2019
@UziTech UziTech mentioned this issue Jun 28, 2019
Merged
4 tasks
@UziTech
Copy link
Member

UziTech commented Jun 30, 2019 •
edited
Loading

v0.6.3 fixes this. Thanks for reporting it.

demo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@UziTech UziTech

Labels
L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix breaks
2 participants
@UziTech @fdietze