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]: App Flickers When Collapsing "Previous Responses" After Choosing Multiple Incorrect Options #5688

Closed
TanishMoral11 opened this issue Feb 3, 2025 · 3 comments
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Low Low perceived user impact (e.g. edge cases). Work: Low Solution is clear and broken into good-first-issue-sized chunks.

Comments

@TanishMoral11
Copy link
Collaborator

Describe the bug

The app flickers when expanding and collapsing the "Previous Responses" section after choosing multiple incorrect options in the "Fraction" exploration.

Steps To Reproduce

  1. Open the "Fraction" exploration.
  2. Choose 2-3 multiple incorrect options.
  3. Click on "Previous Responses" to expand it.
  4. Immediately collapse it.
  5. Observe that the app sometimes flickers.

Expected Behavior

The app should not flicker when expanding or collapsing the "Previous Responses" section.

Screenshots/Videos

Flicker_Issue.webm

What device/emulator are you using?

Pixel 7 Pro API 29

Which Android version is your device/emulator running?

No response

Which version of the Oppia Android app are you using?

No response

Additional Context

No response

@TanishMoral11 TanishMoral11 added bug End user-perceivable behaviors which are not desirable. triage needed and removed triage needed labels Feb 3, 2025
@aadityaverma2011
Copy link

i would like to work on this issue . please assign it to me

@TanishMoral11
Copy link
Collaborator Author

Hi @aadityaverma2011 , we’d love to hear your proposed solution. If it sounds good, we’ll assign it to you and you can create a PR.

@adhiamboperes adhiamboperes added Impact: Low Low perceived user impact (e.g. edge cases). Work: Low Solution is clear and broken into good-first-issue-sized chunks. labels Feb 4, 2025
@BenHenning
Copy link
Member

@adhiamboperes curious on your thoughts--do you have a specific solution in mind (for marking 'work: low'?

I'm marking this as a duplicate of #3006 since it's the same issue. I have a strong suspicion that this can only be fixed by introducing data diffing, and we know from past history that's not a trivial project.

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. Impact: Low Low perceived user impact (e.g. edge cases). Work: Low Solution is clear and broken into good-first-issue-sized chunks.
Development

No branches or pull requests

4 participants