When deleting a server the app becomes unresponsive due to pointer-events not being handled

(#5) Bug Fixed community ui

Observed behaviour

Currently pointer events are not handled anymore. Expected behaviour The app should restore it's click handling back to normal.

Reproduction steps

  1. Create a Community
  2. Delete the community
  3. Enter your password in the double verification modal
  4. Now the app is not usable

Details

Summary

It seems like the modal-handling is broken. When I opened a modal (for example via deleting a server), the pointer-event handling is not restored requiring you to reload the application.

Area

Frontend / Web

Environment

  • OS: CachyOS
  • Browser: AppImage application
  1. The pull request fluxer#141 mentions this post Closed
  2. The pull request fluxer#141 was closed without merging Closed

Merged posts

These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.

Merged from #90 Interface stops working on MacOS after deleting community

RexSystemoriginally by @ONikumu on GitHub

Report details

Summary

После нажатия кнопки "удалить сообщество" сообщество удаляется и после этого интерфейс перестает реагировать и с ним становится невозможно взаимодействовать.

Steps to reproduce

  1. Откройте настройки сообщества
  2. Нажмите удалить сообщество

Environment (optional)

  • OS: MacOS Sonoma 14.4.1

Merged from #42 Deleting Community Freezes Desktop App

Ladyoriginally by @kenderbard on GitHub

Report details

Summary

When deleting a community/guild from the Desktop App, the deletion goes through but the app is then frozen.

Steps to reproduce

  1. Using the Desktop app, delete a community.

Environment (optional)

Linux Mint 22.3 Cinnamon on kernal 6.17.0.14-generic

2 comments

Sign in with Fluxer to comment and vote.
Comment by @ooTruffle
RexSystem 1 vote originally by @ooTruffle on GitHub
This also happens on a m4 mac mini running the native arm app
Comment by @Jiralite
RexSystem 1 vote originally by @Jiralite on GitHub
This should be fixed. Please let us know if you can still reproduce this!