wordpress-mobile / wordpress-mobile/WordPress-Android

[Reader Customization] Adjacent posts don't get customization when swipping after preference update

Open
#20,622 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug Reader
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

Expected behavior

The customization preferences are applied to all post details.

Actual behavior

If, right after changing the reading preferences, we swipe to an adjacent, already loaded, post, it doesn't apply the customization.

More info here: pcdRpT-6gD-p2#comment-9765

Steps to reproduce the behavior
  1. Go to Reader
  2. Go to Subscriptions
  3. Open a Post
  4. Swipe a few posts
  5. Open Reading Preferences
  6. Change some settings
  7. Go back to save the preferences
  8. Swipe back to a post that was previously loaded
  9. 🔍 The post detail screen for that post does not have the latest Reading Preferences
Tested on Samsung A14, Android 13, JPAndroid 24.6-rc-2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Reader flow described: change Reading Preferences, save them, then swipe back to an already loaded adjacent post. Trace how preference updates reach post detail screens and verify that previously loaded posts receive the latest customization; done means all post details reflect the updated preferences.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.