[Feature Request]: Prevent Page Reload on "Send Message" and Add Success Toast Notification

[akshadgujarkar]

Is there an existing issue for this?

• I have searched the existing issues

Feature Description

Current Behavior:
--> When the "Send Message" button is pressed, the page reloads, disrupting the user experience and providing no immediate feedback regarding the success of the message submission.

Expected Behavior:
1)On pressing the "Send Message" button, the page should not reload.
2)Instead, a toast notification should appear confirming that the message has been sent successfully.

Use Case

Implementing this feature will significantly improve the user experience by eliminating unnecessary page reloads, which disrupt the flow of the application. The addition of a toast notification provides immediate visual feedback, ensuring users know when their message has been successfully sent.

Benefits

Improve the user experience by eliminating unnecessary page reloads, which disrupt the flow of the application.

Add ScreenShots

Screen.Recording.2024-10-18.174918.mp4

To prevent the above situation which we can see in the video When the "Send Message" button is pressed, the page reloads, disrupting the user experience and providing no immediate feedback regarding the success of the message submission.

Priority

High

Record

• I have read the Contributing Guidelines
• I'm a GSSOC-EXT contributor
• I'm a HACKTOBERFEST contributor
• I have starred the repository

[akshadgujarkar]

could u please assign issue to me I am really wanna work on it

[GAVINESHWAR]

@akshadgujarkar, please go ahead to make better user experience.

[akshadgujarkar]

@GAVINESHWAR kindly review the PR. if any changes let me know

[akshadgujarkar]

Hi, @GAVINESHWAR , @jeevan10017 I wanted to provide an update regarding this issue. I am currently unable to work on it due to a new issue I've encountered with the cloning process caused by an invalid file path in the .github/workflows directory. Pls solve that issue #295 . By resolving this issue then only I will able to clone this repo and started working issue #269 .

Please do not close this issue; I intend to solve this issue once the new issue #295 is fixed. Thank you for your understanding!

[GAVINESHWAR]

@jeevan10017, many of the contributors are getting the same issue

[jeevan10017]

@akshadgujarkar @GAVINESHWAR once confirm it. Is this issue solved ?.

[GAVINESHWAR]

I Think it is not solved I will clone once and check it.