Skip to content
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

JM - (SPARCForms) View Response Likert Bug #1299

Merged
merged 2 commits into from May 9, 2018

Conversation

jwiel86
Copy link
Contributor

@jwiel86 jwiel86 commented Apr 13, 2018

https://www.pivotaltracker.com/story/show/156545721

When viewing a user's Survey or Form response with a Likert scale, the user is able to click other Likert options' labels and change the selected radio button. This will not change the data but the radio buttons should not be selectable.

@jwiel86 jwiel86 force-pushed the jm-view-response-likert-bug branch from c7bb80e to 8cad785 Compare April 13, 2018 15:48
@@ -36,7 +36,7 @@
.form-group
%p.question-description
= raw(question.description)
.question-options
.question-options{ id: ['new', 'edit', 'preview'].include?(action_name) ? '' : 'disable-likert' }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will give us multiple elements with the same ID which breaks DOM conventions. Is it possible to use a class instead?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, this can cause lots of problems, especially in forms.

@jleonardw9 jleonardw9 dismissed kayla-glick’s stale review May 8, 2018 15:26

Id was changed to class, issue is resolved.

@Stuart-Johnson Stuart-Johnson merged commit 4fc5f85 into v3.3.0 May 9, 2018
@Stuart-Johnson Stuart-Johnson deleted the jm-view-response-likert-bug branch May 9, 2018 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants