Created attachment 107983 [details] sample file Steps: 1) Open attached file 2) Select part of the italics, non-bold or colored of the text 3) On style drop down, open drop down submenu, and click to update the style based on selection. Version: 4.4.0.0.alpha0+ Build ID: 3b6ee58652d99accd610425264114d1d5b3330df TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-10-15_21:41:26
After discussing the style issue with Sophi on IRC regarding her similar bug 84999, it seems that you need to modify the full text defined in a particular style in order for 'update to match selection' to work with or without a selection. This behaviour is different from MS Word which applies the style based on the selection or the cursor position.
Hi, so confirmed as discussed with Jay on irc. The style is not updated if the paragraph selection is partial, you have to select the whole paragraph to be able to update the style. Tested with Heading1 paragraph style. Sophie
*** Bug 84999 has been marked as a duplicate of this bug. ***
If I'm not mistaken, this is behaviour from the old days, so > Inherited from OOo
Question is whether this must be changed.. When you have to select a whole paragraph and all formatting must be the same: - it prevents messing up formatting (in at least the selected paragraph) - there is no change that one updates to a font that is not intended. Ideas for WontChange / WorksForMe ?
hmm, it is not needed to select the whole paragraph if it has the same formatting. And the style will not be updated if the paragraph is not equally formatted. Works like this in 3.3.0 and 5.0.0beta1
Punting this over to ux-advise for other people's opinion. For me, if it didnt act like i expected it to act, it should have given me an error or something rather than it doing nothing and not telling me why its doing nothing. Also the label is called 'update the style based on selection', its not called 'update the style based on the style of the entire paragraph'.
(In reply to Yousuf (Jay) Philips from comment #7) > For me, if it didnt act like i expected it to act, it should have given me > an error or something rather than it doing nothing and not telling me why > its doing nothing. Yep, a message would be appropriate. > Also the label is called 'update the style based on > selection', its not called 'update the style based on the style of the > entire paragraph'. LOL, it was called "Update style" previously ;)
There is an issue, and misconceptions, on how a style is applied and how a style can be modified. Bug 89960 -- Suggestion to Change Style Behavior in Relation to Direct Formatting, as well as bug 83726 -- Applying Styles Does Not Consistently Set Character Properties, are the broader case. However, the .uno command linked to this menu item functions correctly to modify Paragraph style to match selection, but only when selection is a whole paragraph and only when all characters in the paragraph have the same direct formatting. Regards the the sample file, it contains a paragraph defined in Title Paragraph style so has bold black text, but also with several direct formattings applied to individual characters, e.g. italics and red color--and all as Default Character style. Because the direct formatting are applied to individual characters and not over the entire paragraph they are invalid attributes for defining/modifying a paragraph style. Even the "New Style from Selection" from the Paragraph styles or the Character styles tabs of the Styles and Formatting content panel on the Sidebar will not work with partial selections from Paragraphs. The other facet is that Character styles when applied are not merged with Paragraph styles--and Paragraph styles do not influence Character styles--it is one or the other, and you either need to define a new Paragraph style or a new Character file--but must choose. Individual characters or strings can take or define/modify Character styles--but Paragraphs are monolithic. But, even with a correct understanding of the relationship between component styles, and of direct formatting the behavior of some of the .uno commands are faulty, for example bug 70759 -- Apply Style toolbar "Clear formatting" action does not clear the formatting but sets style "text body".
(In reply to V Stuart Foote from comment #9) Thanks for your coherent explanation, Stuart!
*** Bug 91207 has been marked as a duplicate of this bug. ***
*** Bug 92021 has been marked as a duplicate of this bug. ***
** 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
Still reproducible. Version: 6.3.0.0.alpha0+ Build-ID: be8897d9c63a77b223a9c0aed1d2eb689e0e0082 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-02_04:49:04
Please add keyword 'needsUXEval' and CC 'libreoffice-ux-advise@lists.freedesktop.org' if input from UX is needed.
Dear Yousuf Philips (jay) (retired), 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
cf comment #9, we can simply close as NAB