Created attachment 124039 [details]
Document to copy table from
Can't select a table and replace it with another table
If table selected from a website or another odt document and wish to paste it _instead_ of a table from other document, table which pasted does not replace existing table but that second table is inserted into each row of existing table:
- open 'copy-from' document
- position in cell 'E'
- hit CTRL + A twice to select whole table
- open 'paste-to' document
- from within cell '5' hit CTRL + A twice (to select whole table)
- hit CTRL + V
Result: see 'result.odt'.
Tables are replaced correctly if _whole document_ is selected with CTRL + A, but that will delete content outsite the table which is not desired.
Created attachment 124040 [details]
Document to copy table to
Created attachment 124041 [details]
Or try by copying from document 1 to document 2. Result is in 3. Adding new examples because sometimes pased correctly.
Created attachment 124042 [details]
Created attachment 124043 [details]
Created attachment 124044 [details]
I can not confirm with 18.104.22.168; win7
Tested both of your examples. Please test with newer version. Thanks
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux
Build ID: 89f508ef3ecebd2cfb8e1def0f0ba9a803b88a6d
CPU Threads: 2; OS Version: Linux 3.16; UI Render: default;
Locale: hr-HR (en_US.UTF-8)
Reproducable every time (with documents 1, 2 and 3).
Try exit Quicklunch, restart Windows machine, open document 1
- Enable Edit mode (opens from here in read-only)
- position in row 4, cell 2 (after space mark)
- hit CTRL+A twice
- close document one
- open document 2
- enable edit mode
- position i row 4, cell 2 (after space mark)
- hit CTRL + A twice
- hit CTRL + V
see result in document 3
Don't just exit Quicklanch, disable it and then restart. And it seems it's important to close first document before opening second.
Second table pastes correctly if first document stays opened, it pastes wrongly only if first document closed and then opened second.
Is it LO bug at all?
Can't reproduce on
Linux jessie 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) i686 GNU/Linux
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
It's the same operating system, difference is in processor, LO version and desktop environment: first test is under KDE (from Debian Jessie official repository), and this one is Cinnamon (from Debian Jessie official repository).
I was wrong, can't reproduce it with LO 4.4.7 and Intel PC only with documents I attached here.
But it's reproducible _always_ if table copied from web page:
- go to http: //hjp.znanje.hr /index.php?show=kosi_oblici&id=fFhgXA%3D%3D [remove spaces from url]
- copy word list form the web page to a new ODT document
- position inside the table
- now do CTRL + A twice to select only table and then do CTRL + V
Please, confirm this bug.
Long tables can force LO to go into a loop and one table with 20 rows can make 300 new pages and LO is not responsive during that time (for two or three minutes).
(In reply to Kruno from comment #12)
> - go to http: //hjp.znanje.hr /index.php?show=kosi_oblici&id=fFhgXA%3D%3D
> [remove spaces from url]
> - copy word list form the web page to a new ODT document
> - position inside the table
> - now do CTRL + A twice to select only table and then do CTRL + V
64-bit, KDE Plasma 5
Build ID: 22.214.171.124 Arch Linux build-1
CPU Threads: 8; OS Version: Linux 4.5; UI Render: default;
Locale: fi-FI (fi_FI.UTF-8)
Possible duplicate of bug 45307.
It doesn't hang in LO 126.96.36.199 on Debian Buster (curr testing) on 32-bit processor.
Copied table still does not replace old one and it pastes content into it, but at least it does not hang.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Since that link is not correct, I set to Needinfo for the reporter to write reproducible steps.
Please see bug 37223 and test with current LO 6.1 or 6.2.