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

bug: Reply visually disappears if replying to an older message #912

Open
2 tasks
Fledrox opened this issue Jun 27, 2023 · 0 comments
Open
2 tasks

bug: Reply visually disappears if replying to an older message #912

Fledrox opened this issue Jun 27, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Fledrox
Copy link

Fledrox commented Jun 27, 2023

What happened?

Replying to a message that is old enough to show the "viewing older messages" button, the reply seems to disappear. Said message shows up when reloading the webpage/client. It seems to only do it when reply mention is enabled.

Reproduce steps:
Go in a channel with enough messages
Scroll up until it shows "viewing old messages"
Reply to a message with mentions on, type anything then send without scrolling back or clicking back on "viewing older messages"

Branch

Production (app.revolt.chat)

Commit hash

5363ff2

What browsers are you seeing the problem on?

Vivaldi 6.1.3035.84 (Stable channel) stable (64-bit)

Relevant log output

[FSM Anonymous] Object
Session.tsx:171 [FSM Anonymous] Object
proxy:1     Failed to load resource: the server responded with a status of 400 ()
/api/channels/01FBCT2PXQC0SSH6GD3V1BEHRP/messages/01H3JNA1KH3Z6YBVYSHK069CQ5:1     Failed to load resource: the server responded with a status of 404 ()
createError.js:16 Uncaught (in promise) Error: Request failed with status code 404
    at createError$1 (createError.js:16:15)
    at settle (settle.js:17:12)
    at XMLHttpRequest.Ar (xhr.js:66:7)
/api/channels/01FBCT2PXQC0SSH6GD3V1BEHRP/messages/01H3JNA1KH3Z6YBVYSHK069CQ5:1     Failed to load resource: the server responded with a status of 404 ()
createError.js:16 Uncaught (in promise) Error: Request failed with status code 404
    at createError$1 (createError.js:16:15)
    at settle (settle.js:17:12)
    at XMLHttpRequest.Ar (xhr.js:66:7)
/api/channels/01FBCT2PXQC0SSH6GD3V1BEHRP/messages/01H3JNA1KH3Z6YBVYSHK069CQ5:1     Failed to load resource: the server responded with a status of 404 ()
createError.js:16 Uncaught (in promise) Error: Request failed with status code 404
    at createError$1 (createError.js:16:15)
    at settle (settle.js:17:12)
    at XMLHttpRequest.Ar (xhr.js:66:7)
/api/channels/01FBCT2PXQC0SSH6GD3V1BEHRP/messages/01H3JNA1KH3Z6YBVYSHK069CQ5:1     Failed to load resource: the server responded with a status of 404 ()
createError.js:16 Uncaught (in promise) Error: Request failed with status code 404
    at createError$1 (createError.js:16:15)
    at settle (settle.js:17:12)
    at XMLHttpRequest.Ar (xhr.js:66:7)

Desktop

  • Yes, this bug is specific to Revolt Desktop and is not an issue with Revolt Desktop itself.

PWA

  • Yes, this bug is specific to the PWA.
@Fledrox Fledrox added the bug Something isn't working label Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant