Description: In the example file, if you put cursor before sinADB, type space key, formula is pushed to right, but sinADB is not changed. If you delete some character, e.g. delete s from sin, only formula position is updated. Steps to Reproduce: 1.Open attached file, put cursor before sinADB, type some character or space bar 2. formula is pushed to right, but sinADB position not updated 3. if you delete some character from sin, only formula is updated Actual Results: page contents not updated immediately, if you press F5 twine, the page is refreshed Expected Results: each time you input or delete character, the page contents should be immediately updated Reproducible: Always User Profile Reset: No Additional Info: The following version has the same bug. Version: 7.3.4.1 (x64) / LibreOffice Community Build ID: 13668373362b52f6e3ebcaaecb031bd59a3ac66b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: zh-CN (zh_CN); UI: en-US Calc: CL
Created attachment 180322 [details] example file to show the bug
Reproduce in the following versions: Version: 7.4.0.0.alpha1+ / LibreOffice Community Build ID: f817b3de1aa827d93e2a622735c4d570514f4849 CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: en-US Calc: threaded (Debian sid package) Version: 7.3.4.1 / LibreOffice Community Build ID: 30(Build:1) CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: en-US Debian package version: 1:7.3.4~rc1-1 Calc: threaded When I typed a space, only the formula object moved. "SinADB" moved when the cursor was moved or when it was clicked.
When insert a shape object on the same line as the formula object and set the anchor as a character, this bug will not appear.
Reproducible with: Version: 7.3.2.2 (x86) / LibreOffice Community Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: es-ES Calc: threaded Redrawing the screen (i.e., changing zoom level, underline changes in the automatic spell checking) made it updated as expected. NOT reproducible with: Version: 7.2.7.2 (x86) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: en-US Calc: threaded
Please retest with a new version, works well for me. Retested with Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Dear water.qian, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear water.qian, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp