Description: With paragraph styles it is possible to create a nested hierarchy of styles with percentage font sizes, where the percentage is calculated based on the parent style. These values are automatically updated when the parent value changes. Character styles ought to work the same way, but they don't. Bug 108498, Comment 4 states: > It should be based on its parent style. > > It is in ODF 20.183fo:font-size > "In contrast to XSL, percentage values can be used within common styles only > and are based on the font height of the parent style rather than to the font > height of the attributes neighborhood. Absolute font heights and relative > font heights are not supported." > > So with the current fo:font-size it is not possible to base the character > font-size on the paragraph in which the character is, which gets this style > applied. > > The percent values is written to file and the percent value is calculated, > when the style is defined in the beginning. But the text in the document is > not updated, when the font-size of the parent character style is changed. > > If you revisit the character Font dialog page and click on OK without any > changes, then the text in the document is updated. There are several problems with this. The issue in this bug is the fact that child styles do not update to reflect changes in the parent. (The fact that the values displayed by the interface are misleading given the actual behavior, and the fact that the advice in the last paragraph fails in certain circumstances will be addressed separately, if need be.) The fact that percentage font sizes in character styles do not work like they do in paragraph styles is confusing to the user. Also, the need to have to manually update all child styles almost completely defeats the purpose of having percentage font sizes at all. I can't see anything in the ODF spec that implies that there should be a difference, either in the quote above or elsewhere (I looked as best I could). Can we get the character style behavior changed to match paragraph styles? If so, the other issues I mentioned will be taken care of as well. Steps to Reproduce: 1. Create a character style with a parent and a percentage font size. 2. Change the parent font size Actual Results: The child style font size does not change Expected Results: The child style font size should change Reproducible: Always User Profile Reset: Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
I can confirm the problem on 5.3.4. I created two character styles, the second a child of the first one with font set at 200%. After applying the second style to some text I went to the first character style and changed the font from 12pt to 24pt. Result: the text with the second character style did not change. Finally I entered the second character style and clicked on "OK" without changing anything: only then the text with the second character style was updated. Note that the style preview on the sidebar is updated, but the style applied on the text is not. Only when you edit the child style the system recognize the changes on the parent style.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problem still exists in Version: 6.1.0.0.beta2+ (x64) Build ID: 67a56897ec1e4f2bab2c3291b8dd225710d2ae29 CPU threads: 8; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@62-TDF, Branch:libreoffice-6-1, Time: 2018-06-29_13:19:46 Locale: de-DE (en_US); Calc: CL
Dear Kenneth Hanson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No change as of v6.3.2.2.
Dear Kenneth Hanson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Problem still present in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded Same behavior as described in Comment 1