There are FAR too many to document in any digestible way, so there is no plan to document them. Also, a “simple” documentation could actually be dangerous because this is an advanced feature; documenting something like
.tr with the expectation that a user would know ALL of the places the “tr” class is in use would be preposterous (as would updating the documentation whenever we make the smallest change).
Suppose we documented
.tr as a class, and a user decides that simply knowing about the existence of
.tr is enough to modify their CSS files. They might just be trying to change their table, but now they’ve modified their Tables, Alarm Journal Table, Alarm Status Table, and Easy Chart with a style change.
It’s sort of like “with great power comes great responsibility” - but we’re electing to allow users to learn how to use the power through experience before we give them superpowers and let them loose in the city.
There’s a small chance during major version changes, because we take that as our opportunity to institute changes which might break APIs/scripts/custom modules. I can’t think of anything like this that changed for 8.1.0, so you’re safe until at least 8.2.0.