For example, with a checkbox or an edit-text field, I believe this should be an exposed, adjustable option. Of course, it should be enabled by default, but an advanced user, when creating their own things, should have the choice to enable or disable it.
There is a Github issue since Aug. 2021, but nobody took the chance to add the functionality to all relevant widgets and create pull requests.
Yes, it seems this has been a consistent topic of discussion, but there haven’t been many PRs submitted. I haven’t mastered JavaScript yet, but I hope a solution can be implemented soon, especially since the 5.4.0 release is still a long way off.
Another possibility is to have two parallel discussions. We could continue working on features that don’t affect backward compatibility in the 5.3.x branch, and save features that do affect it for the 5.4.x branch. However, this might be a difficult approach to manage.
We do not have the man-power to maintain 2 stable branches.
No, I wasn’t suggesting we maintain two branches. I meant we should be selective about features. Features that break backward compatibility could be merged after the 5.4.x release, while features that don’t could continue to be updated and merged into later versions of 5.3.x. Of course, this is just a suggestion. The development team would make the final decision.
I belive that is exactly what pmario refers to in his reply about not having man-power for it.