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

[BUG]: Submit Button Stays Disabled After Linking Items in Drag-and-Drop Input #5592

Open
Rd4dev opened this issue Dec 10, 2024 · 2 comments · May be fixed by #5597
Open

[BUG]: Submit Button Stays Disabled After Linking Items in Drag-and-Drop Input #5592

Rd4dev opened this issue Dec 10, 2024 · 2 comments · May be fixed by #5597
Assignees
Labels
bug End user-perceivable behaviors which are not desirable. good first issue This item is good for new contributors to make their pull request. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Low Solution is clear and broken into good-first-issue-sized chunks.

Comments

@Rd4dev
Copy link
Collaborator

Rd4dev commented Dec 10, 2024

Describe the bug

In the Drag and Drop Sort Interaction when items are linked to represent equivalence (e.g., 0.6 and 3/5), the linked states are not recognized as different from the unlinked states, keeping the submit button disabled.

Steps To Reproduce

  1. Open the "Prototype Exploration".
  2. Play through to the "Second Drag & Drop interaction".
  3. Arrange the items in the order: 0.6, (unlinked) 3/5, 0.46, 0.35 and attempt to submit.
  4. The app will indicate that the order is incorrect.
  5. Click submit again with unchanged solution.
  6. The Submit button will be disabled mentioning to arrange first.
  7. Link 0.6 and 3/5, arranging them as 0.6, (linked) 3/5, 0.46, 0.35.
  8. Despite the correct arrangement or change in the link states, the submit button will still remain disabled, preventing the successful submission of the answer.

Expected Behavior

The submit button should enable immediately after there is a change in the link states.

Screenshots/Videos

constant_reload_merge_state.mp4

What device/emulator are you using?

Pixel 2 [Emulator]

Which Android version is your device/emulator running?

API 28

Which version of the Oppia Android app are you using?

No response

Additional Context

No response

@Rd4dev Rd4dev added bug End user-perceivable behaviors which are not desirable. triage needed labels Dec 10, 2024
@adhiamboperes adhiamboperes added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Low Solution is clear and broken into good-first-issue-sized chunks. and removed triage needed labels Dec 12, 2024
@adhiamboperes adhiamboperes added the good first issue This item is good for new contributors to make their pull request. label Dec 12, 2024
@adhiamboperes
Copy link
Collaborator

adhiamboperes commented Dec 12, 2024

Suggested fix to follow example in #5323.

@TanishMoral11
Copy link
Contributor

Hey @adhiamboperes , Can I work on it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug End user-perceivable behaviors which are not desirable. good first issue This item is good for new contributors to make their pull request. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Low Solution is clear and broken into good-first-issue-sized chunks.
3 participants