Added PopUp for Email Confirmation

[Himanshu-639]

fixes #4049

This PR implement a Popup for email confirmation before sending the verification email to user.

[coderabbitai[bot]]

Walkthrough

This pull request implements an email confirmation popup for the signup page and refactors the corresponding Selenium test. The HTML template now includes a hidden popup with "Confirm" and "Edit Email" buttons and associated JavaScript to handle its display and actions upon signup. Additionally, the Selenium test for signup has been refactored to utilize WebDriverWait for element interactions in place of direct element access and explicit sleep calls.

Changes

File(s)	Change Summary
website/templates/account/signup.html	Added an email confirmation popup with a new <div>, confirm and edit buttons, a <style> block for a hidden state, and JavaScript to manage popup display and form actions.
website/tests.py	Refactored the test_signup method in MySeleniumTests to replace direct element access and explicit sleep calls with WebDriverWait for improved test stability.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant F as Signup Form
    participant P as Email Confirmation Popup
    participant JS as JavaScript Handler

    U->>F: Click Signup button
    F-->>JS: Trigger "click" event
    JS->>F: Prevent default form submission
    JS->>P: Remove hidden class to show popup
    alt User confirms the email
        U->>P: Click "Confirm" button
        P-->>JS: Submit the signup form
        JS->>F: Process form submission
    else User opts to edit email
        U->>P: Click "Edit Email" button
        P-->>JS: Add hidden class to hide popup
    end

Assessment against linked issues

Objective	Addressed	Explanation
Provide a mechanism to confirm and edit the email during user signup (#4049)	✅

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Himanshu-639]

@CodeRabbit pls check if these changes resolves the mentioned issue

[coderabbitai[bot]]

[!TIP] For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# Get PR details including title, description, and issue reference
gh pr view 4064 --json title,body,commits,files

# Get the list of files changed
gh pr view 4064 --json files --jq '.files[].path'

# Get the diff to see the actual changes
gh pr diff 4064

Length of output: 10172

---

@Himanshu-639 I've reviewed the changes in your PR, and they look good for resolving issue #4049.

Your implementation adds a confirmation popup that shows the user's email address before sending the verification email, with options to either confirm or edit the email. The key components you've added are:

1. A popup dialog in the signup.html template that displays the user's entered email
2. JavaScript logic to show this popup when the signup button is clicked
3. "Confirm" and "Edit Email" buttons that either proceed with submission or allow the user to modify their email
4. Updated test code that accommodates this new flow

These changes effectively implement the requested feature of adding an email confirmation popup before sending verification emails to users. The implementation is clean and focused on solving the specific issue.

Code Analysis Tools

Tool Analysis Results

CodeRabbit ran static analysis tools on your files and found the following: <toolResults></toolResults>

No specific issues were found in your files. You can proceed with your changes.

[Himanshu-639]

@DonnieBLT sir please review this PR.

[DonnieBLT]

unconfirmed emails should expire after a certain time releasing the username so this is not an issue.