Description: Have had this problem as long as I can remember: if I set text to shrink to text box in Master, this is not passed on to slides Steps to Reproduce: 1. start new presentation 2. change master to do text shrinking 3. (v6.3 does not do it in Master either - prev versions did) 4. create new slide 5. type lots of text Actual Results: text does not shrink overflows the bottom of the slide heading is messed up so that slides do not look consistent Expected Results: should shrink Note: if tick fit to frame , then stretches text to plainly look strange Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: PresentationDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 6.3.0.0.alpha0+ Build ID: e4c2d0bb57ab8ea8f5c400d103d01376b8140f22 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-11-30_21:37:10 Locale: en-GB (en_ZA.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 147264 [details] text shrinking problem
Created attachment 147266 [details] sett master - text option
Created attachment 147267 [details] master - position and size settings
Created attachment 147268 [details] master - force postion and size
Created attachment 147269 [details] create slide - title not inheriting settings from master note: nor does it do so when I select the master and say apply to slide
Created attachment 147270 [details] slide body text box als doe not act, plus fit to frame Can someone explain why one would want to do fit to frame for text - and get the distortion of the text
(In reply to Elmar from comment #0) > Actual Results: > text does not shrink > overflows the bottom of the slide > heading is messed up so that slides do not look consistent > > Expected Results: > should shrink > Note: if tick fit to frame , then stretches text to plainly look strange I can confirm this behavior on my installation! Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.18.04.2 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3_kde5; Gebietsschema: de-AT (en_GB.UTF-8); Calc: group threaded
Hi Elmar, I'm sorry but I have problem to follow the steps. I don't understand the screenshots attached. Could you please create and attach a screencast showing the steps? There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web). I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested screencast is provided.
Dear Elmar, 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 Elmar, 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