Still an issue on v1.17.41.
Any plans by developers to address the problem, or just continue ignoring it?
Still an issue on v1.17.41.
Any plans by developers to address the problem, or just continue ignoring it?