Open Bug 1973605 Opened 1 month ago Updated 17 hours ago

Copied text has frequent line breaks inserted when pasted into Notion

Categories

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

Firefox 140

Tracking

(Webcompat Score:5, Webcompat Priority:P2)

UNCONFIRMED
Webcompat Score 5
Webcompat Priority P2

People

(Reporter: keesmail, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:platform-bug, webcompat:site-report)

User Story

platform:windows,mac,linux
impact:annoyance
configuration:general
affects:all
branch:release
diagnosis-team:dom
user-impact-score:200

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

Steps to reproduce:

Copy one or more paragraphs from an article with embedded links (this seems to be key) and paste it into a Notion page (on the web version on Firefox or Chrome or the Notion desktop app). I'm not sure if other websites have this issue too.

Actual results:

Line breaks will be inserted, sometimes near links but at other points as well.

Expected results:

When copying the text in Chrome, no extra line breaks are inserted.

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → General
Product: Firefox → Firefox for Android
Product: Firefox for Android → Firefox
Component: General → Site Reports
Product: Firefox → Web Compatibility
Webcompat Score: --- → 1
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: 1 → 6
Priority: -- → P2
Webcompat Score: 6 → 5

(I am going to take a look this one)

Depends on: 1498271

Oh, I forgot to mention, the new pasted content in Notion page has white-space: break-spaces; as well, and if I disable the white-space: break-spaces; from DevTools, the content displays as expected (no line break). So this must be related to bug 1498271.

I'm not sure if it's bad to add a comment just to ask, but I'm wondering if any progress has been made on this.

You need to log in before you can comment on or make changes to this bug.