Why aren't class properties browsable in the Variables pane anymore in R2019a (during debug)?

Up to my previous MATLAB version (2017a), I have always been able to use the Variables browser to browse through the hierarchy of objects of my own classes during debugging, also through instances of other classes encapsulated as properties. Like you can for simpler data types like structures. A screenshot from the Variables panel in 2017a:

In 2019a however, when I open an object variable from the Workspace panel while debugging, I get this:

Additionally, superclass properties aren't even shown anymore! This renders the Variables panel pretty much useless in my case, since despite Matlab's limitations I heavily rely on OOP. The only way to retreive a value from a property buried more than one level deep is via the command line, which is not very practical. When I exit the debugger (and hence lose the workspace of the method scope), any object variables in the workspace can be browsed like they used to in older versions.

Besides this, can I just say how it astounds me why the IDE is never brought to a level where building more serious software becomes a pleasure, and if anything, it only gets worse? I would be so much less unhappy if Mathworks decided for one year not to include any new features, but just focussed on building an IDE which can actually refactor, keep track of variable declarations, have proper auto completion, etc etc. I am more and more motivated to completely move to Python and even consider porting all Matlab code rather than keeping maintaining it.

Anyway, does anyone know whether this changed "functionality" is actually intentional or a bug? If it is the former, I really wonder what Mathworks are thinking...

[Adam]

Yes, this does seem an annoying change, even though I rarely use the variable browser for this, almost always the command line. It does show public superclass variables though. I don't recall it ever showing private ones.