1902004 - chatgpt.com - No text copied in input field

Status: VERIFIED FIXED

(Web Compatibility :: Site Reports, defect, P2)

Description

[railioaie]

Environment:
Operating System: Windows 10
Firefox version: Firefox Nightly 129.0a1 (2024-06-11) / Firefox Release 127.0

Preconditions:
Clean profile

Steps to reproduce:

1. Navigate on https://chatgpt.com/
2. Ask something
3. After ChatGPT responds, hover the mouse over the text you sent and a pencil mark will appear
4. Click the pencil mark
5. Select the text and copy
6. Paste the selected text in the input field
7. Observe the page

Expected Behavior:
The text should be copied in input field

Actual Behavior:
No text copied in input field

Notes:

• Reproduces regardless of the status of ETP
• Reproduces in Firefox Nightly, Firefox Release
• Does not reproduce in Chrome

Comment 1

[railioaie]

Attachment: 12.06.2024_15.38.14_REC.mp4

Comment 2

[Ksenia Berezina [:ksenia]]

The problem here is that window.getSelection().toString() returns an empty string, only in Firefox:

  e.preventDefault();
  const n = window.getSelection();
  if (n && n.rangeCount > 0) {
    const a = n.getRangeAt(0).cloneContents();
    t(a);
    const o = document.createElement('div');
    o.appendChild(a);
    const s = o.innerHTML;
    e.clipboardData.setData('text/html', s),
    e.clipboardData.setData('text/plain', n.toString())
  }

This depends on bug85686 (and related bug1527627)

Comment 3

[mike.clark.8192]

Ksenia Berezina wrote:

The problem here is that window.getSelection().toString() returns an empty string, only in Firefox

I stepped through the current ChatGPT minified JS in the Firefox debugger and verified that this is still the case as of time of this writing.

I also wrote an Unlicense'd userscript workaround that targets chatgpt.com. The userscript is on greasyfork.org. I'm not going to link to it because I don't think the code is relevant to the proposed fix path that runs via bug85686 and I don't want to come off as self-promoting or fishing. However, it's easy enough to find on the site as it is listed publicly.

Comment 4

[gianni]

problem still present in firefox
132.0.2 (64-bit)

is it this one?
https://greasyfork.org/en/scripts/508994-firefox-chatgpt-fix-copy-while-editing(In reply to mike.clark.8192 from comment #3)

Ksenia Berezina wrote:

The problem here is that window.getSelection().toString() returns an empty string, only in Firefox

I stepped through the current ChatGPT minified JS in the Firefox debugger and verified that this is still the case as of time of this writing.

I also wrote an Unlicense'd userscript workaround that targets chatgpt.com. The userscript is on greasyfork.org. I'm not going to link to it because I don't think the code is relevant to the proposed fix path that runs via bug85686 and I don't want to come off as self-promoting or fishing. However, it's easy enough to find on the site as it is listed publicly.

Comment 5

[Sean Feng [:sefeng211]]

railioaie, can you still reproduce this? Clicking the pencil shows the text for me now. Thanks!

Comment 6

[railioaie]

Hello, Yes it's still reproducible for me.(see attachments)

Comment 7

[railioaie]

Attachment: 17.01.2025_12.32.15_REC.mp4

Comment 8

[Sean Feng [:sefeng211]]

Oh I see, thanks, sorry I misunderstood the bug

Comment 9

[addisongourluck]

Still happening. Constant thorn in the side.

Comment 10

[Hsin-Yi Tsai (she/her)[:hsinyi]]

I confirmed this issue was resolved after bug 85686 landed.

Comment 11

[Randell Jesup [:jesup] (needinfo me)]

That's great. That is also blocking a similar webcompat bug in gemini

Right now bug 85686 is nightly-only; I've pinged Sean about how we get it to release

Comment 12

[Calin Tanase]

No longer reproduces on Nightly (138), still reproducible on Release (136) and Beta (137).

Comment 13

[James Graham [:jgraham]]

Putting this back on the diagnosis queue so that the bug on shipping bug 85686 to release can be added as a blocker.

Comment 14

[Jeff Muizelaar [:jrmuizel]]

I confirmed that this works in Nightly. Jesup's going to file a bug about letting the behaviour ride the trains.

Comment 15

[Hsin-Yi Tsai (she/her)[:hsinyi]]

We already have that bug 1954979 which landed already.
I guess I should just set the bug dependency.

Comment 16

[Randell Jesup [:jesup] (needinfo me)]

Shipping to release in 139 -> Fixed

Comment 17

[Calin Tanase]

Verified, the issue no longer reproduces.

Tested with:

• Browser / Version: Firefox 139.0-candidate build 1
• Operating System: Windows 10