https://bugs.documentfoundation.org/show_bug.cgi?id=160231
--- Comment #23 from Stéphane Guillou (stragu) <[email protected]> --- (Telesto replied before me but here's my original reply anyway.) (In reply to MB from comment #20) > Unfortunately I completely disagree with you and I was really upset sawing > that you marked this bug as duplicate. Let me explain. Sorry that upset you, but let me clarify what the process usually is: - someone reports an issue. - if we don't have precise steps to reproduce the bug, there isn't much we can do to fix the problem - once we have steps, we often try to minimise them to really pinpoint what the root problem is - that allows developers to zero into where in the code the process fails, and eventually fix it > First of all did you notice that with my methodology many images (which are > in fact groups) get lost and the problem is not only "image" at row 106? As said above, we focus on a precise, reproducible example so we can investigate further. I understand other groups are affected in your document, I am not ignoring that. > Secondly, In my everyday usage of the file I never resize or move images, > they are all in the middle of their cells anchored there and I never touch > them. But after some edits and saves this happens again. People asked me to > create a methodology to replicate the issue for them to see it and I > searched for it showing a methodology but this doesn't mean this is the real > problem. It's just a way to see with your own eyes the proof that there is > an issue. And thank you for finding those steps. It allowed me to look further into it. > My bug report here so refers to the random lost of "images" (which proved to > be image groups) when editing the file, not when resizing the images. The groups are in fact not lost. They are moved elsewhere. If you repeat the steps you gave us in comment 18, you will still be able to find the group we used as an example "组合 166", you can see it in the Navigator and double-click it to select it. It was moved down in the sheet. > If you > mark this as duplicate the issue here is closed and all the info that comes > with it. I spent too much time on this to accept your last comment as the > same as my issue. And we appreciate you taking the time to help out! The information is not lost, it available publicly and isn't going anywhere. Often, when a bug is fixed, QA will check that indeed everything described in the duplicates is also fixed. And when bug 160369 gets fixed, you can check that it indeed resolved your overall issue. Duplication is important so we can focus our attention on root causes of problems. You will find many reports on this bug tracker that are marked as duplicates of one issue even though the symptoms described are _very_ different. Sometimes, a bug has many different consequences. > What you describe is another issue. >From the information we have, and to the best of my knowledge, bug 160369 is the root cause (or at least one of the causes) of your problem. Other related problems that need fixing are, for example, bug 160329, bug 152635, bug 147420. > If you find the reason why the group of images are lost without any resize > of them just by editing the document, I may accept that it is related Bug 160369's steps does not require any resizing. And again, the group is not "lost", it is merely moved. Does that make more sense? -- You are receiving this mail because: You are the assignee for the bug.
