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

motion forwarding: motion layout broken after forwarding #2288

Closed
MSoeb opened this issue May 12, 2023 · 0 comments · Fixed by #2293
Closed

motion forwarding: motion layout broken after forwarding #2288

MSoeb opened this issue May 12, 2023 · 0 comments · Fixed by #2293
Assignees
Milestone

Comments

@MSoeb
Copy link

MSoeb commented May 12, 2023

Description: A forwarded motion has layout issues, if it is opened via the link in the original motion. The page is broken and need to be reloaded to see and use all buttons. This problem also occurs, if the user opens the original motion link in the forwared motion. In both directions the content of the motion is not fully loaded and broken.

original motion with a forward link:
Screenshot_20230512_155206

situation after click on forward link:
Screenshot_20230512_155256

page reload -> whole content appears
Screenshot_20230512_155333

view after click on original motion link: for example: the livestream can't be closed. page is broken and needs reload.
Screenshot_20230512_155412

Reproduction:
pre-condition: two meetings with forwarding options needed.

  1. open meeting A
  2. open motions
  3. create a motion
  4. forward the motion to meeting B
  5. click now on the forward link in the original motion
  6. -> now in meeting B the layout is broken -> reload page
  7. navigate back to the original motion by clicking on the link of the original motion
  8. -> layout once again broken

What should happen:
By opening the links to switch back and forth, the layout should work without reload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants