wordpress-mobile / wordpress-mobile/WordPress-Android

Reader settings: unfollowing a site and making a configuration change removes it from list of followed sites

Open
#11,358 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

This issue was raised while reviewing #11343

Expected behavior

In Reader > Settings > Followed Sites, when unfollow a site and make a configuration change, we want the unfollowed site to remain listed.

Actual behavior

In Reader > Settings > Followed Sites, when unfollow a site and make a configuration change, we get the unfollowed site is removed from the list.

Steps to reproduce the behavior
  • Go to Reader settings
  • Select the Followed Sites tab
  • Unfollow a followed site and make a device screen rotation
  • Check that the unfollowed site is removed from the list

NOTE with some more context taken from here

Currently we keep a site in the list when unfollowed in case the user changes his mind and we remove it once the user leave that screen; what happens is that we end up removing it from the list also on config changes in that same screen that seems an unwanted behaviour.

Tested on [Pixel 3 Emu], Android [API 29], WPAndroid [14.2 with Information Architecture active]

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 Reader settings under Followed Sites: unfollow a site, rotate the device, and inspect when the site is removed. Done means the unfollowed site remains listed through configuration changes on that screen and is removed only after leaving it.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.