Currently it is impossible to transform the same node with multiple transformations using a single selector as all selectors must be unique, but it is possible to write different selectors that happen to address the same node(s). When this happens, the result is untested and not well defined.
While untested, transforming the same node in a way that does not touch the children (or modify scoped-parameters) should work as expected. That is, if you apply both content and class transformations to the same node(s), it should work as expected.
If the children (and/or scoped-parameters) are modified, then it is undefined what will happen. Likely it would be order-dependent.
Need to test the former case to ensure it works as expected and clearly define what should happen in the latter case.
Currently it is impossible to transform the same node with multiple transformations using a single selector as all selectors must be unique, but it is possible to write different selectors that happen to address the same node(s). When this happens, the result is untested and not well defined.
While untested, transforming the same node in a way that does not touch the children (or modify scoped-parameters) should work as expected. That is, if you apply both content and class transformations to the same node(s), it should work as expected.
If the children (and/or scoped-parameters) are modified, then it is undefined what will happen. Likely it would be order-dependent.
Need to test the former case to ensure it works as expected and clearly define what should happen in the latter case.