RANT - The developers to my mind still don't fully comprehend how this UI element locking policy change VERY BADLY affects accessibility. They have stated they won't fix this issue until 5.19 if at all and ONLY if new bugs are filed for plasmashell and panel separately because they will have to re-code how they work too. The far simpler option would be to reverse the policy changes but apparently that also isn't possible without breakages or conflicting with the 'new' policy.
IF they had to live with the issue themselves they'd understand and see where they'd majorly screwed up.
How are new or existing users with palsy, Parkinson's or essential tremor supposed to know and be able to enter terminal commands to lock everything down which was possible before with a single click in the UI?
I won't go into the technicalities of how this remains an issue here because they were already explained in detail and essentially outright dismissed on bugzilla.
Apparently if I want this fixed I have to file a new bug for something they have already dismissed off-hand in a bug report about this eaaxcat function? I REALLY cannot be arsed now and if you or any other developers can't see why then what's the point anyway?
@Pointedstick as you probably worked out already I am pissed off to put it politely as possible because you clearly still don't see the full picture despite it being explained to you VERY clearly when you asked what the issue was.
I get it's difficult to put right in a point release but it should never have been released in this form without due diligence of such issues in the first place. This may seem unduly harsh to you but it really is not, it is fair and constructive criticism of the Project's planning and decision making process. To re-emphasise I am not trying to insult anyone here before you go on the defensive again.
How can you put it right? PLEASE take this under your own wing and file those separate bug reports yourself based on all the information I already posted to the bug thread.
