This might be limited to the french locale that uses commas instead of dots. 1) New void draw document 2) create a rather long slanted line 3) try to make it 0,0 cm width So far so good : this is a vertical line Now any change you make to the width text field won't be reflected to the object: this is unexpected! The workaround is to use the mouse to change the shape of the line, and edit the field properly. Of course it also happens in the other direction. A wrong behavior that might be related: 1) New void draw document 2) create a rather long slanted line 3) select the whole contents of the vertical text field 4) enter "0,5" You won't even get a chance to enter the separator. What you only get is 0,00 cm and you fall back into the above problem.
Hello, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 128562 [details] one vertical line, one slanted Expected behavior: 1) select the green line 2) open the position and size pane (from the contextual menu) 3) edit the fields 4) press the OK button Changes are reflected to the green line Unexpected behavior 1) select the red line 2) open the position and size pane (from the contextual menu) 3) edit the width fields 4) press the OK button Changes in the width field are not reflected to the red line whereas changes in the other fields are taken into account. Possible solutions : 1 - deactivate the width or height field when this kind of problem is about to occur 2 - or take the base point into account to decide on which side to extend the object.
Dear Bug Submitter, 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-20170531
Dear Bug Submitter, 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-20170628