https://bugs.documentfoundation.org/show_bug.cgi?id=156424
ady <adylo811...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Ever confirmed|0 |1
Status|RESOLVED |NEW
--- Comment #4 from ady <adylo811...@gmail.com> ---
I am resetting this from FIXED to NEW, for more than one reason.
Setting this to FIXED is inadequate, as there is no commit/patch that is known
to solve it. At most, it would be WFM.
Additionally, if indeed this is a problem in a current version (such as 7.5
ATM), and it happens to work correctly in a development version that will only
be available as stable in about 6 or 7 months, it could mean several
(unnecessary) reports might get filed in the following months. Leaving this
report opened as NEW would help users in their searches (not so much when it is
set as resolved).
Moreover, there is a chance that, leaving this open for now, someone might find
what exactly makes this work correctly in LO 24.2 (which I have not tested
myself), thus allowing the possibility to cherry-pick or back-port such patch
to LO 7.5 (or 7.6, which is not yet released as stable ATM).
This report might eventually be closed as resolved, either by committing a
patch to 7.5, 7.6, or when those versions are no longer supported.
--
You are receiving this mail because:
You are the assignee for the bug.
