Timeline-specific status state should be stored #55

New Issue

shadowfacts · 2019-11-19T03:30:27Z

shadowfacts commented

2019-11-19 03:30:27 +00:00

This is because the expand/collapse state isn't stored, and so it resets to collapsed by default. When the table view scrolls back up the cell is no longer collapsed, so the content height changes, so the content below the previously collapsed cell appears to jump up.

The expanded state should be persisted somewhere, possibly somehow related to the lifetime of the post in the specific timeline/conversation/profile controller.

This is because the expand/collapse state isn't stored, and so it resets to collapsed by default. When the table view scrolls back up the cell is no longer collapsed, so the content height changes, so the content below the previously collapsed cell appears to jump up. The expanded state should be persisted somewhere, possibly somehow related to the lifetime of the post in the specific timeline/conversation/profile controller.

shadowfacts added the

bug

label 2019-11-19 03:30:27 +00:00

shadowfacts changed title from ~~Expanding a post, then scrolling down past it, then back up, results in the content jumping~~ to Timeline-specific status state should be stored

2019-11-22 14:37:32 +00:00

shadowfacts commented

2019-11-22 14:38:23 +00:00

This same mechanism should be expanded to include the current hidden state of sensitive attachments.

shadowfacts referenced this issue from a commit

2019-11-29 02:52:56 +00:00

Store status collapse state in containing view controller Also, copy the state between screens, so e.g. expanding a status in the timeline and then opening that conversation already has that status expanded. This intentionally doesn't store the sensitive attachment visibility state, since showing text when not necessary is less dangerous than for images. (Possibly a preference for this in the future?) Closes #55

shadowfacts closed this issue

2019-11-29 02:52:56 +00:00

Sign in to join this conversation.