I'll revisit an old suggestion: Can we create a mechanism where a problem author can mark an entire question or a specific input field to be omitted from the MathQuill handling?
Even just the second idea with the use of CSS :not() should help solve the problem of an overly broad initial selector. (https://developer.mozilla.org/en-US/docs/Web/CSS/:not)
For the general "skip MQ" for this problem, I'm not sure what would be the simplest mechanism, maybe setting a CSS class or a JavaScript variable which when true would "turn off" the MathQuill processing for the current page (or better yet only for DOM descendants of where the class was set).
For the specific input fields exception - let's assume that we will soon be able (in PG) to add additional class names (and style attributes, etc.) to input fields via some sort of extension of the ans_rule() method, so we could have a skipMQ class for this purpose. (See openwebwork/pg#444 ) I intend to work on implementing that within the next few months (and sooner would be better for me also).
Note: The openDiv() support already supports creating a DIV with a given class name. See: openwebwork/pg@da0f007#diff-2c3e0f1c9ff2f13866441f52d449f855
Originally posted by @taniwallach in #1071 (comment)
I'll revisit an old suggestion: Can we create a mechanism where a problem author can mark an entire question or a specific input field to be omitted from the MathQuill handling?
Even just the second idea with the use of CSS
:not()should help solve the problem of an overly broad initial selector. (https://developer.mozilla.org/en-US/docs/Web/CSS/:not)For the general "skip MQ" for this problem, I'm not sure what would be the simplest mechanism, maybe setting a CSS class or a JavaScript variable which when true would "turn off" the MathQuill processing for the current page (or better yet only for DOM descendants of where the class was set).
For the specific input fields exception - let's assume that we will soon be able (in PG) to add additional class names (and style attributes, etc.) to input fields via some sort of extension of the
ans_rule()method, so we could have a skipMQ class for this purpose. (See openwebwork/pg#444 ) I intend to work on implementing that within the next few months (and sooner would be better for me also).Note: The
openDiv()support already supports creating a DIV with a given class name. See: openwebwork/pg@da0f007#diff-2c3e0f1c9ff2f13866441f52d449f855Originally posted by @taniwallach in #1071 (comment)