https://bugs.documentfoundation.org/show_bug.cgi?id=132864
--- Comment #19 from [email protected] --- (In reply to Dieter from comment #9) > Since we haven't a guideline for anchoring ... it is very difficult > to assess for users and also for people in QA, if a behaviour is expected > or not ... So an overview about anchoring would reduce work and would > make QA more efficient. A few suggestions to first responses to "anchoring" reports about objects not positioned as expected. 1. Check to see if positioning options have been provided in the bug report. If not, then NEEDINFO to get them. 2. If the OP does not report what the person is trying to accomplish, then use NEEDINFO to find out. Many options are available, with remarkable capabilities, but it is necessary to evaluate what a person is trying to accomplish and what positioning options have been chosen to achieve that goal. It is possible that a person has chosen the wrong option (or misunderstands how the option is supposed to operate) in relation to the goal. (In principle: https://help.libreoffice.org/7.4/en-US/text/swriter/01/05060100.html gives full information about positioning options). (meanwhile, FTR -- there are several inaccuracies in that page (e.g., bug 148901, bug 148902, bug 148903, bug 148904, bug 148486, bug 148483) and some implementation bugs in some of the positioning options). 3. If a person starts with the idea that "anchor only" is sufficient for positioning, then it will be impossible to communicate meaningfully or to make reliable STR. There are interactions between "what positioning is desired" and what positioning options are chosen, which is why it is necessary to know the two pieces indicated in the first two points. I believe steps 1 and 2 may help OP and QA to direct their attention and communication in a way that will reduce the need to send queries to Design Team. -- You are receiving this mail because: You are the assignee for the bug.
