1610182 - Clipboard actions with Disqus comments are broken

Status: ASSIGNED

(Web Compatibility :: Site Reports, defect)

Description

[cleek]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

Enter some text in a Disqus comment box. Copy / paste some text into that same
box.

Actual results:

Unpredictable number of newlines are inserted in and around existing text. New text is pasted to a unpredictable location (sometimes it's where the cursor is, sometimes it's at the start, sometimes the end).

Expected results:

It should behave like a normal text.

Comment 2

[Daniel Kolsis]

Hello, I managed to reproduce the issue and it seems that it's been here for a while. I haven't been able to find a specific build in which it was introduced, but I do have this:

• last good build: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=505bafeafb66b0083ce1fca8eec2d061f1a5ebb7&tochange=2667f0b010c959940d7a12b4311d54a6abd74ac5
• first bad build: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=505bafeafb66b0083ce1fca8eec2d061f1a5ebb7&tochange=17e47288c2249ac21bd2d0585b19c835984ed32b

Setting component to Core > DOM: Editor.

Comment 3

[Edgar Chen [:edgar]]

I managed to reproduce this issue, but it seems not to match the regression window in comment #2 given that I am able to reproduce this issue even on 57.

My STR is,

1. go to https://www.getlektor.com/docs/guides/disqus/
2. enter some text in comment box
3. press Ctrl+a to select all text.
4. press Ctrl+c to copy the text.
5. press Ctrl+v to paste text multiple times.

Could you share the you STR? Thanks.

Comment 4

[Daniel Kolsis]

I took a better look at the issue and found that pasting a string, hitting Enter/Return to go on a new line and pasting the string again produces the issue as well. I managed to go back quite a lot, I have no idea how deep the rabbit hole goes, as I've managed to reproduce the issue even in Firefox 36. I don't think there's a point to go any further, as this is definitely not a recent regression.
One more note, Chrome and Opera seem to not have any problems with this input field, however, Edge and Internet Explorer seem to have similar problems here.

Comment 5

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

This is the site's web-compat issue. On Chrome, it uses contenteditable="plaintext-only", but it probably won't be standardized. Therefore, the copying data is different on Gecko vs. Blink. On Gecko, each line is wrapped with a <p> element. That's oddly serialized by themselves. They insert <p><br></p> after every <p> element. That's the reason why the empty lines are inserted repeatedly. This serializing is anyway broken on Chrome is you copy such HTML fragment from anywhere (including Chrome itself). E.g., copy from:
data:text/html,<div contenteditable><p>abc</p><p>def</p><p>ghi</p></div>. So, the developer of Disqus should fix this by themselves, otherwise, their users cannot paste multiple paragraphs from any HTML on any web browsers as their users expected.

Comment 6

[cleek]

The difference between how Firefox handles this and how Chrome handles this is like night and day. In Chrome, it works fine - copy/paste multiple paragraphs, no problem at all. Copy/paste is unusable in FF w/Disqus - line breaks are inserted everywhere; spacing between paragraphs is doubled or tripled; pasting more text causes existing text to be reformatted and even more new lines are added. I've seen nothing like this at all in Chrome.

Comment 7

[Peter Saint-Andre [:stpeter]]

I'm seeking an intro to someone at Disqus...

Comment 8

[cleek]

In the meantime, clipboard interaction with the edit control on Disqus comments remains essentially unusable.

Comment 9

[Mike Taylor [:miketaylr]]

stpeter, were you able to find any contacts into Disqus, by chance?

Comment 10

[RNicoletto]

(In reply to Mike Taylor [:miketaylr] from comment #9)

stpeter, were you able to find any contacts into Disqus, by chance?

Unfortunately, getting in touch with Disqus team is not easy.
According to their Support Page (https://disqus.com/support/) users can inquiry:

1. The Knowledge Base, where there is no trace of this problem.
2. The Community Support, which is a mess, without any index or search functionality.

The only alternative is this: "Direct support is reserved for paying publishers and large forum moderators.".

Comment 11

[Karl Dubost💡 :karlcow]

There are people who can be contacted through GitHub.
https://github.com/orgs/disqus/people

for example https://github.com/tail (email there)

or https://github.com/tterb at https://brettstevenson.io/contact/

Comment 12

[Peter Saint-Andre [:stpeter]]

:miketaylr I'm working on it!

Comment 13

[Oana Arbuzov [:oanaarbuzov]]

The issue still occurs.
https://prnt.sc/10i3bz5

Tested with:
Browser / Version: Firefox Nightly 88.0a1 (2021-03-09)
Operating System: Windows 10 Pro

Comment 14

[Ksenia Berezina [:ksenia]]

I've reached out on GitHub.

Comment 15

[Raul Bucata]

I was able to reproduce the issue:

https://prnt.sc/NeqqvmShJ2L9

Tested with:

Browser / Version: Firefox Nightly 102.0a1 (2022-05-05) (64-bit) /Chrome Version Version 101.0.4951.54 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64

Notes:

1. Reproducible regardless of the status of ETP.
2. Reproducible on the latest build of Firefox Nightly.
3. Works as expected using Chrome.

Comment 16

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Comment 17

[Raul Bucata]

The issue is still reproducible

Tested with:

Browser / Version: Firefox Nightly 111.0a1 (2023-01-16) (64-bit)
Operating System: Windows 10 PRO x64