<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - "Hide Rows" causes Calc to hang CALC UI"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=144131#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - "Hide Rows" causes Calc to hang CALC UI"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=144131">bug 144131</a>
from <span class="vcard"><a class="email" href="mailto:henrik.palomaki@yandex.com" title="Henrik Palomäki <henrik.palomaki@yandex.com>"> <span class="fn">Henrik Palomäki</span></a>
</span></b>
<pre>(In reply to Timur from <a href="show_bug.cgi?id=144131#c3">comment #3</a>)
<span class="quote">> Uwe and Henrik, if you can repro with master, just mark New.
> If you cannot, you need to test back with reporter's version - if you can
> there, that's likely WFM.
> If repro with master, important is to see whether Inherited from OO or
> regression, so please test with OO and older LO. Finding exact LO branch
> (like 6.2) is necessary for most useful action, bibisect (even if you will
> not find it, mark BibisectRequest will get someone do it). It can also start
> im LO as ImplementationError or incomplete fix.
> Handling so many LO versions is easy in Windows with SI-GUI that downloads
> and extracts LO, without installation, so only disk space is required.</span >
Thanks for your advice. I'll try to mark bugs as new when they are reproduced
with a master version.</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>