Description: Typing on a page works fine, but after inserting a larger image (experienced issues with a 7.5 MB photo) the display of typed words becomes really sluggish, it takes more than a couple of seconds before newly typed letters appear. Steps to Reproduce: 1. Typing on an empty page works fine 2. after inserting a larger image (experienced issues with a 7.5 MB photo) the display of typed words becomes really sluggish, it takes more than a couple of seconds before newly typed letters appear. 3. opening or navigating to another (new) page in the same document, typing works fine. After returning to the page with the large image, typing becomes very sluggish again. Actual Results: Typing very sluggish after inserting a larger (7.5 MB) image Expected Results: Newly typed characters should be displayed instantly. Displaying speed of newly typed characters should not be affected by the presence of any additionally added content on a page. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no Typing on a page works fine, but after inserting a larger image (experienced issues with a 7.5 MB photo) the display of typed words becomes really sluggish, it takes more than a couple of seconds before newly typed letters appear. When opening or navigating to another (new) page in the same document, typing works fine. After returning to the page with the large image, typing becomes very sluggish again. This issue apparently occurs with larger images only, I did not experience any trouble with small (100 kB) images I have tested this issue on several of my OS's, and can be reproduced on all of them: Win10 32-bit, Win10 64-bit, Ubuntu 16.04 (32-bit) User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:57.0) Gecko/20100101 Firefox/57.0
Looks like there is a previous report with the exact same problem, bug 112568. Can you please attach an example document to the older report? *** This bug has been marked as a duplicate of bug 112568 ***