added a comment - - edited
I did this already, but I hesitate to commit it, since it seems it will be smarter to keep the inline CSS.
The classes I created are non-semantic like bankvisible and quizwhenbankcollapsed - they do not add any semantics since they are bound to the very behaviour of the css properties, so they will just be badly named - keeping the semantics in the HTML and the style in the CSS is the idea of classes, after all. We won't reach there here, just as we do not with the special javascript class added to body (though that one may have technical reasoning).
It does not seem to make any sense to theme that specific CSS, it will just add another reference, making the code harder to read. Where is the benefit?
Sub-task
Closed
Minor
I did this already, but I hesitate to commit it, since it seems it will be smarter to keep the inline CSS.
The classes I created are non-semantic like bankvisible and quizwhenbankcollapsed - they do not add any semantics since they are bound to the very behaviour of the css properties, so they will just be badly named - keeping the semantics in the HTML and the style in the CSS is the idea of classes, after all. We won't reach there here, just as we do not with the special javascript class added to body (though that one may have technical reasoning).
It does not seem to make any sense to theme that specific CSS, it will just add another reference, making the code harder to read. Where is the benefit?