<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Character transparency should apply to objects anchored as character" href="https://bugs.documentfoundation.org/show_bug.cgi?id=144021#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Character transparency should apply to objects anchored as character" href="https://bugs.documentfoundation.org/show_bug.cgi?id=144021">bug 144021</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=144021#c3">comment #3</a>) > For good reason. Most users likely don't see the type of anchor as a reason > to follow character or paragraph properties. The anchor is rather an > attribute of the object itself and consequently you have to set transparency > or other attributes on this object. Please note that in this case, we are talking specifically about *as-character* objects, that for users look just like a special kind of (big) character - users do not look at "anchor" here, they see an object as a part of a selection, when they start in one part of text, and select through another part, including an as-character object. And applying a transparency to the selection, they would see part of selection not following the command. In this case, I'm the user who made the request, trying to do exactly what I describe here, and seeing the inconsistency that made me to open specific properties of the as-character image, and setting the transparency there explicitly, independent on setting those for the containing text paragraph.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>