Pasting table from Word causes infinite rows
Describe the bug When pasting a table from Word (desktop app) Nexctloud Text somehow inserts empty rows above the pasted content. The empty rows fill the screen. As I scroll down to the content, more rows are added above the content continiously filling the screen with empty rows.
Expected behavior Expected behaviour is no empty rows inserted, or at least not an infinite amount of empty rows.
Screenshots If applicable, add screenshots to help explain your problem.
Word with tables, marked (grey) text is copied to clipboard
When pasted into Text, screen is filled with empty rows
Screenshot as more and more rows added above the pasted content. I need to be quick to get this screenshot before the empty rows filled the whole screen.
Client details:
- OS: Windows 10
- Browser: Firefox (112.0.2 (64-bit))
- Word: Microsoft® Word for Microsoft 365 32-biters MSO (Version 2304 Build 16.0.16327.20200)
- Device: Desktop
Text app version: 3.7.2
Nextcloud version: 26.0.1
Looks similar to #2708
I tried to reproduce this with a simple table, but on macOS it seems that word is adding the content as an image to the clipboard which is pasted instead.
@Hephi2 Since you're the one with WIndows in our team, any chance you have Word around and can reproduce this?
If reproducible it might be worth to see if https://github.com/nextcloud/text/pull/4285 helps
This seems to be a problem with the Firefox Browser. Any table copied into text in the Firefox Browser is buggy: For me, every change in the table triggers creating a new row at the top of the table. This should not be related to word but only to Firefox. #4285 does not solve this problem.
As discussed also happens with pasting the html table from https://github.com/nextcloud/text/issues/2708
I no longer can reproduce this problem when copy & pasting tables from Word (MS 365 Online) into Text. Tables with multiline contents and merged cells get mangled, but the infinite rows issue is no longer reproducible to me. I wonder whether this got also fixed in #2708.
Everybody still experiencing this, please comment and ideally provide a clear reproducer.