j
k
j a
j l
Today I've tried go back to 2.4.18 release and in the same configuration there isn't this bug.
So it is problem in 2.4.19 and 2.4.20.
Pavel
Back to the thread
Back to the list