The new tree-format class browser is great; however it doesn't work for classes that are subclass of intersectionOf two other classes.
Setup:
<rdfs:subClassOf>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
</owl:intersectionOf>
</owl:Class>
</rdfs:subClassOf>
</owl:Class>
To me, ideally C should appear in both A and B branches, as for example it does in Protege class browser in this situation, but minimally it should appear somewhere (top level?) in the tree
Get:
C appears in neither A nor B, nor anywhere else.
In the old 2.x 'leaf-class' view, if A, B and C had instances then all three classes were browsable so the new behaviour is a regression.