Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Issues with copying post source from revision history

Parent

Issues with copying post source from revision history

+2
−1

When I try to copy and paste text out of a revision history for a question or answer, I notice that:

  • Blank lines are not preserved
  • If I copy the entire text of a revision, the entire thing will also be indented by four spaces on each line, and have two blank lines added on each end. (Skipping even a single character at either the beginning or end seems to avoid this.)

(This caused problems for me lately, as I attempted to use a revision history to create a Git backup of changes to a post for my personal records.)

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Related feature request (5 comments)
Post
+2
−0

I see the described behaviour in Firefox but not in Chromium.

  • Operating System: Fedora 38
  • Firefox version: 116.0
  • Chromium version: 115.0.5790.102

Example of a Post History page where this behaviour occurs:

The initial revision (#1), where there is no side by side diff, just the text of the original post, shows no problem.

The edits (#2 onwards) have a before and after version of the post content, and copying either before or after version gives the problem.

The problem occurs when copying from the first character to the last character, whether including the final newline or not. Apart from that final newline (which shows as a space at the end of the final line when selected), omitting a single character from the beginning or end of the visible text results in copying only what is seen. If all of the visible text is copied, pasting elsewhere results in each line having 4 leading spaces, and there are 2 blank lines before the start of the visible text, and 2 blank lines after the end of the visible text, and any existing blank lines within the post content are omitted.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

I am using Firefox 115.0.2 on Mint 20.3. I can't get *intervening empty* (i.e. blank) lines to copy r... (4 comments)
I am using Firefox 115.0.2 on Mint 20.3. I can't get *intervening empty* (i.e. blank) lines to copy r...
Karl Knechtel‭ wrote over 1 year ago

I am using Firefox 115.0.2 on Mint 20.3. I can't get intervening empty (i.e. blank) lines to copy regardless of what is selected. Single newlines are preserved, but multiple newlines seem to collapse to a single newline. This is inconvenient for me because of the extra lines I had to add in order to get mixed HTML and Markdown to work properly.

I normally have clipboard events disabled for security reasons, but I tried temporarily enabling them and it did not resolve the issue.

trichoplax‭ wrote over 1 year ago

I was focused on the indentation and didn't picked up this, but I can confirm I also see this (no blank lines). I'm not sure how to avoid this with copying from rendered HTML, but an option to view as raw text would ensure the correct number of newlines.

Karl Knechtel‭ wrote over 1 year ago

Should status-norepro be removed, then?

trichoplax‭ wrote over 1 year ago

I personally believe it should be removed. I flagged your question for moderator attention directly after posting this answer, so when someone sees the flag they can decide whether to remove the norepro tag.