[Libreoffice-ux-advise] [Bug 112852] Should unapplying Bold remove the attribute or force text to Regular?

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sun Oct 8 11:56:42 UTC 2017


https://bugs.documentfoundation.org/show_bug.cgi?id=112852

--- Comment #8 from Yousuf Philips (jay) <philipz85 at hotmail.com> ---
(In reply to Octavio Alvarez from comment #6)
> Then I chose option (a) ;-) Out of kidding, option (a) is not a bad option
> either and I am open to it if it makes it easier to understand. It's a sign
> that it may be easier for other users too.

Option (b) is the only correct option in my view. I tried the same example in
MS Word and the result was quite strange as step 5 resulted in 'LibreOffice'
being bold and the other text being not bold, and step 6 resulted in all the
text being bold and no longer looking like step 4.

> My suggestion is [so far] strictly about *the application / un-application
> of default formatting* because it clearly breaks the user expectation as
> currently implemented. It has [so far] nothing to do with changing styles.
> Changing a style is just the easiest way to expose the broken behavior.
> Another way is through the paintbrush as DF plays a role on how it works:

Please provide an example that is only DF, if it has nothing to do with styles,
and not using paintbrush, as that opens up a different set of problems.

> 6. Place cursor between "a" and "i" in "Plain". Hit Paintbrush. Hit the "a"
> in "Heading". Nothing happens at all.

this would be a bug in paintbrush in my view.

> 7. Place the cursor between "r" and "c" in "ForcedRegular". Hit Paintbrush.
> Hit the "a" in "Heading". The word "Heading" turns regular.

I hit the "a" and only the "a" turned regular, so i'm assuming you clicked on
the entire word.

> When applying Direct Formatting, attributes that end up matching the
> underlying styles [1] should be unset.

I could agree with you and Heiko on this behaviour.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Libreoffice-ux-advise mailing list