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

--- Comment #8 from ady <[email protected]> ---
(In reply to four from comment #7)
> Definitely an RTL problem.  I wrote this in the original bug report.

>From comment 0, I did not get the impression that an RTL worksheet was
essential. I did not understand the term "particularly reproducible" as being
exactly the same as "Definitely". FWIW, I indeed tested the case with RTL.

I can (sometimes) reproduce the behavior with a new file, but it is still not
clear (at least not to me) the exact steps, or rather the reason(s) in order to
trigger it.

For instance, in comment 0, step 3 is unclear, or perhaps even unneeded. I take
note of the size and position of the image (in order to be able to compare it
with the reloaded file later on), but IDK what should I "verify", or whether
the image needs to be anchored / positioned / sized in some particular way.

Additionally, step 4 in comment 0 might be optional too. The reason I am unsure
about it is because I can replicate the behavior with one new file (with a RTL
worksheet), but then when I start the whole procedure again with a new file
there is some minor detail that makes the resulting behavior different (i.e. I
cannot replicate the same issue).

It is important to note that, after the problem is seen on a file, I no longer
need to make changes in order to trigger it (i.e. step 4 in comment 0); every
save+reload shows the image closer to the right side of the main area (i.e.
closer to column A). Repeating the save+reload multiple times eventually makes
the image completely disappear; that is, not only from the main area, but from
the file itself. At that point, the image is not listed in the Navigator, and
the size of the file has shrunk.

One time I was able to replicate the resulting behavior with a new file (but
not always), and with no certainty of the (real) essential steps or their
order. IOW, further investigations are required. The questions I posted in
comment 6 are still relevant.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to