Created attachment 189203 [details] List issues in direct formatting The remarkable spotlight features introduced in Writer 7.6 (kudos to Jim Raykowsky) is very handy to help in spotting direct format issues, even those issues not covered by the "Clean Direct Formatting" (Ctrl+M) command, which applies only to character formatting. The image atached shows the issue with lists (taken from the file WG7617-Fields.odt) * The first and second paragraphs of the list (1 and 2) were cleaned. * The second an other list entries has direct formatting issues, indicated by the hash in the spotlight indicator and a different indent of the paragraph, even when the paragraph style is the same (#67). The direct formatting is actually a list applied on top of the "Numbering 1" paragraph style (#67) which has its own list associated ("Numbering 1" homonym). To clean the list DF, I had to place cursor on the list and the cycle-click on the corresponding list icon on the top toolbar until the paragraph extra list is removed. Object: Extend the "Clean Direct Formatting" command (swriter/.uno:ResetAttributes) to clean lists as well. By removing the extra list on top of a paragraph with list style By saving the paragraph list number if the list is restarted at this location.
(In reply to Olivier Hallot from comment #0) > taken from the file WG7617-Fields.odt Where can I find this document?
Created attachment 189224 [details] Source file with issue
The list labels (1. 2. 3. or 1) 2) 3) etc.) are always applied (or acknowledged) as CDF. Happens also for new documents. Mike, are List Id and List Label String CDF or just a variable attribute of the paragraph? And in any case, can we suppress the false attribution on the highlighting, Jim?
(In reply to Heiko Tietze from comment #3) > Mike, are List Id and List Label String CDF or just a variable attribute of > the paragraph? Of the paragraph. Showing as character formatting is a bug.
I just discovered that when you clean the lists (bullet or numbers) so no hashed color on the paragraph style, then on saving and reloading the document the hash is back.
So bug, no UX needed.