<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Harmony in position settings of different objects"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132864#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Harmony in position settings of different objects"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132864">bug 132864</a>
from <span class="vcard"><a class="email" href="mailto:dgp-mail@gmx.de" title="Dieter <dgp-mail@gmx.de>"> <span class="fn">Dieter</span></a>
</span></b>
<pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=132864#c7">comment #7</a>)
<span class="quote">> whether NAB or INVALID, point is that I don't see need for the same setting
> over different objects. Maybe I'm wrong and you get other opinions.</span >
Heiko, as far as I understand Telesto, that is not the main idea of this
report. Since we haven't a guideline for anchoring (and a guideline could also
define different solutions for different objects), it is very difficult to
assess for users and also for people in QA, if a behaviour is expected or not
and - if it isn't expected - what should be the desired result. Of course we
can alway say "Let's ask Design-Team" but that produces a lot of work for
Design-Team (and especially for you). So an overview about anchoring would
reduce work and would make QA more efficient.
So bug summary might be wrong and perhaps it's not a valid bug report, but I
support that idea (Telesto, do I understand you correctly?)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>