#### Summary: When a text is edited so its width overflows some limit the text disappears. If finally edited to come back below the width limit it reappears. But if is deselected while hidden due to is too large width, the text object is deleted and only be retrieved by undo. #### Steps to reproduce: Unfortunately I have no idea how I got that text object to behave like that. But this is stable in the sense that once obtained this can be reproduced for ever and ever copied, saved and reloaded. The attached files contains the text with the anomaly. - Open the attached file below with Inkscape 1.2.1 (9c6d41e410, 2022-07-14) - Press T to get A cursor - Left-click on the text object to enter edit mode - Press few characters on keyboard to enlarge the string #### What happened? As the result the text object disappears. #### What should have happened? I would have expected that the dotted rectangle get enlarged to fit the whole new entered text. Sample attachments: File with corrupted text field:   #### Version info Inkscape 1.2.1 (9c6d41e410, 2022-07-14) <!--Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below:--> ``` Inkscape 1.2.1 (9c6d41e410, 2022-07-14) GLib version: 2.72.2 GTK version: 3.24.34 glibmm version: 2.66.4 gtkmm version: 3.24.6 libxml2 version: 2.9.14 libxslt version: 1.1.35 Cairo version: 1.17.6 Pango version: 1.50.7 HarfBuzz version: 4.4.1 OS version: Windows 10 21H2 ``` <!--❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports.--> <!--Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file.-->