Trigger a POP MESSAGE when we go back from tutorial page

[manzil-infinity180]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Suppose whenever we creating a tutorial and go back from this page , it trigger a POP message like " are you really want to go back " like this

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

https://github.com/scorelab/Codelabz/assets/119070053/b9fe7906-94f6-4340-bd3f-1935e0514e9a

[Gayathri2522]

Hi @shivareddy6, @ABHISHEK-PANDEY2 , @Sarfraz-droid, I would like to work on this issue, could you please assign this to me

[DhananjayDogne]

I want to work on this issue . Can you please assign it to me.

[ABHISHEK-PANDEY2]

@manzil-infinity180 please elaborate the issues whenever you raise it, it's not giving any clear idea of what you will be implementing .

[imsidkg]

I think that instead of showing a pop-up message of "do you really want to go back", we should implement a modal saying "do you want to save the changes?"

[manzil-infinity180]

I think that instead of showing a pop-up message of "do you really want to go back", we should implement a modal saying "do you want to save the changes?"

Yeah I am also thinking of it @imsidkg

[imsidkg]

@manzil-infinity180 are you woking on it? if not, can i work on it?

[manzil-infinity180]

@manzil-infinity180 are you woking on it? if not, can i work on it?

I am working on it

[rohitPandey469]

While reviewing some ongoing issues, I came across yours, which is suggesting to have a popup on leaving the url but right now it's already implemented in the QuillEditor's Prompt component. The current implementation would have displayed a message, "You have unsaved changes," but I observed that the associated allSaved state is not updating as expected. I've elaborated on this matter in issue #1129 and the corresponding pull request, #1130. Considering that we consistently use the Snackbar component throughout the application, I suggest utilizing it in this context as well. This way, we can provide an additional notification to users about unsaved changes, ensuring a more uniform user experience.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.