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.

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

Extra new line added when copy/pasting from Quill.JS to a notepad #1579

Closed
Natim opened this issue Jul 10, 2017 · 6 comments
Closed

Extra new line added when copy/pasting from Quill.JS to a notepad #1579

Natim opened this issue Jul 10, 2017 · 6 comments

Comments

@Natim
Copy link

Natim commented Jul 10, 2017

Steps for Reproduction

  1. Visit https://quilljs.com/playground/
  2. Enter a multiline text (You can use the Expected behavior content)
  3. Copy the content of the pad and paste it somewhere (The github comment textarea for instance)

Expected behavior:

The content of the pad is pasted as is:

Type something
And then something else
And then again something

Actual behavior:

A new line is inserted between each lines:

Type something

And then something else

And then again something

Platforms:

Firefox / Ubuntu

Version:

1.2.6

@jhchen
Copy link
Member

jhchen commented Jul 16, 2017

Can you check what HTML is being copied? All Quill can potentially control is what it outputs, not how Notepad or any other application interprets that.

@Natim
Copy link
Author

Natim commented Jul 17, 2017

Yes it seems that the fact a <p> is pasted into text as two linebreaks.
A way to fix that would be to allow <br/> instead of <p> everywhere.

@jhchen
Copy link
Member

jhchen commented Jul 18, 2017

What HTML is being copied from Chrome? It does not appear Chrome has this issue.

@Natim
Copy link
Author

Natim commented Jul 18, 2017

You are right, I can't reproduce the error with Chrome, but I can with Firefox.

@Natim
Copy link
Author

Natim commented Jul 18, 2017

For instance this HTML:

<p>Hello</p>
<p>World</p>

@Natim
Copy link
Author

Natim commented Jul 18, 2017

This fixes the issue #861

@Natim Natim closed this as completed Jul 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants