Inconsistency when switching between desktop and phone view #1009

Open
opened 2020-11-14 15:27:45 +00:00 by Duponin · 1 comment
Member

How to reproduce

  1. desktop view
  2. draft a post
  3. resize viewport to switch in phone view
  4. press button to compose a post
  5. draft post disappeared (!) [1]
  6. resize viewport to switch back to desktop view (without closing post composer)
  7. phone message composer is still shown (!) [2]
  8. draft post (from desktop view) appears

(!) are weird behaviors

Explanations

[1]: I would expect to the same post composer buffer from desktop and phone view
[2]: I would expect to have phone message composer to disappear when switching back to desktop view

(Yes, I use Pleroma-FE in phone view when using my desktop)

# How to reproduce 1. desktop view 2. draft a post 3. resize viewport to switch in phone view 4. press button to compose a post 5. draft post disappeared (!) [1] 6. resize viewport to switch back to desktop view (without closing post composer) 7. phone message composer is still shown (!) [2] 8. draft post (from desktop view) appears (!) are weird behaviors # Explanations [1]: I would expect to the same post composer buffer from desktop and phone view\ [2]: I would expect to have phone message composer to disappear when switching back to desktop view (Yes, I use Pleroma-FE in phone view when using my desktop)
Owner

the mobile post modal and the side panel one are different instances of the component, and data is kept in the component and not globally (we can have a lot of post status forms open at the same time in reply forms).

fixing this would involve writing a copy routine to take data from one post form, keep it in global state before the layout changes and copy it to another after the layout changes, it's still possible but maybe not a high priority issue

the mobile post modal and the side panel one are different instances of the component, and data is kept in the component and not globally (we can have a lot of post status forms open at the same time in reply forms). fixing this would involve writing a copy routine to take data from one post form, keep it in global state before the layout changes and copy it to another after the layout changes, it's still possible but maybe not a high priority issue
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe#1009
No description provided.