-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question component - Marking should only be displayed on final question attempt #2796
Comments
Weird. From the code it definitely adds the classes each time, which it definitely shouldn't. QuestionView:onSubmitClicked MatchingView:showMarking |
Ah OK yes IIRC it was adding the classes - but not displaying ticks/crosses. There must be something in the theme preventing ticks/crosses from being displayed until all attempts used up. We should definitely stop the classes from being added in the first place though. |
I suspect something about the styling / version is a reason for it. I do remember a few clients telling us that their users were using the debugger to figure out from the marking classes what the correct / incorrect options are. This will at least help tackle that one at the same time. |
Yeh I have just confirmed that with FW5 it is behaving as you say @moloko |
There was one more on found in this vein. It looks as though it's the template default. That should really only happen if after restoration the |
This change has created couple of issues for MCQs with more than one attempt:
|
the second issue I think can be fixed by adding |
That makes sense. |
the first issue I thought I could fix by adding Equally we could change this line back to |
Just firing up a framework to have a go at it. if (this.get('_isComplete')) return true; Seems a little more robust if you don't mind? I'll revert that line in className to this.model.get('_canShowMarking') from this.model.canShowMarking |
Not at all, presumably that would also mean these lines would then be redundant? And should it be
yep, I think that leaves it consistent with how the or we update those so that they are only added when 'model answer should now be shown' and 'feedback now can be shown'... either way it should be consistent but I'm not 100% sure which is the best |
I agree looking at it again. That was my fault I think. |
@guywillis @kirsty-hames and any other styling folks, would it be easier from your point of view if these classes were always present - or were only added once marking/model answer/feedback should be shown? |
On the whole yes, that is correct. It exposes configurable options as classes should they be required for styling purposes.
Example: https://github.com/adaptlearning/adapt_framework/blob/master/src/core/less/core/button.less#L49 Potentially, I would say, there should be an additional class applied to differentiate between item marking and question marking. This ticket rightly identifies item marking as being the issue (as you can see which answers you got right / wrong on your first attempt) and so tying item marking display to whether a |
Subject of the enhancement
The Question component could benefit from a 'Display Final Marking Only' type setting
Your environment
Steps to reproduce
Create a course with Matching Question components with multiple question stems; each question having only 2 possible answers and the user has 2 attempts.
Expected behaviour
The component could be set to only display marking on the final attempt
Actual behaviour
After the first attempt, the marking is displayed, making it quite obvious to the user what the correct answers are for each Matching Question
The text was updated successfully, but these errors were encountered: