(In reply to comment #16) > Is the problem in the next version (3.5.4) solved?
Joker. I have yet to see any comment by a LO developer on this bug, so it clearly has not been addressed yet.
(In reply to comment #16)
> Is the problem in the next version (3.5.4) solved?
Joker. I have yet to see any comment by a LO developer on this bug, so it clearly has not been addressed yet.