You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System (Linux/Mac/Windows/iOS/Android): Debian GNU/Linux trixie (testing)
Delta Chat Version: 1.48.0
Expected behavior: clicking "Show Full Message…" on a long message should open a new window with the full message.
Actual behavior: After the first time, does nothing.
I received a long message, which did not render fully in the main window. It has a "Show Full Message…" link below it. The first time i clicked that link, it opened a separate window, which contained the full message.
From that window, i chose "File » Close Window" from the menubar, and the window closed as expected.
But now, when i click "Show Full Message…" (on this same message, or on any other long message, including long messages sent as a test after this situation) nothing happens.
I first encountered this while running 1.46.2, but i've since upgraded to 1.48.0 and still nothing happens when i click "Show Full Message…".
no messages appear in the logfile, or on stderr during this click.
In the course of testing this further for replication, i did once get the external window to show again, but i can't figure out what was different about that click compared to any of the dozens of other times that i tried to show any of these large messages. Restarting the app doesn't seem to make a difference either.
The text was updated successfully, but these errors were encountered:
On Fri, Nov 15, 2024 at 05:45 -0800, dkg wrote:
- Operating System (Linux/Mac/Windows/iOS/Android): Debian GNU/Linux trixie (testing)
- Delta Chat Version: 1.48.0
- Expected behavior: clicking "Show Full Message…" on a long message should open a new window with the full message.
- Actual behavior: After the first time, does nothing.
I received a long message, which did not render fully in the main window. It has a "Show Full Message…" link below it. The first time i clicked that link, it opened a separate window, which contained the full message.
From that window, i chose "File » Close Window" from the menubar, and the window closed as expected.
But now, when i click "Show Full Message…" (on this same message, or on any other long message, including long messages sent as a test after this situation) nothing happens.
I first encountered this while running 1.46.2, but i've since upgraded to 1.48.0 and still nothing happens when i click "Show Full Message…".
no messages appear in the logfile, or on stderr during this click.
In the course of testing this further for replication, i did *once* get the external window to show again, but i can't figure out what was different about that click compared to any of the dozens of other times that i tried to show any of these large messages. Restarting the app doesn't seem to make a difference either.
--
Reply to this email directly or view it on GitHub:
#4343
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
I received a long message, which did not render fully in the main window. It has a "Show Full Message…" link below it. The first time i clicked that link, it opened a separate window, which contained the full message.
From that window, i chose "File » Close Window" from the menubar, and the window closed as expected.
But now, when i click "Show Full Message…" (on this same message, or on any other long message, including long messages sent as a test after this situation) nothing happens.
I first encountered this while running 1.46.2, but i've since upgraded to 1.48.0 and still nothing happens when i click "Show Full Message…".
no messages appear in the logfile, or on stderr during this click.
In the course of testing this further for replication, i did once get the external window to show again, but i can't figure out what was different about that click compared to any of the dozens of other times that i tried to show any of these large messages. Restarting the app doesn't seem to make a difference either.
The text was updated successfully, but these errors were encountered: