Skip to content

Improved Contact UI styling#297

Closed
pradnya1212 wants to merge 1 commit intoEswaramuthu:mainfrom
pradnya1212:improve-contact-ui
Closed

Improved Contact UI styling#297
pradnya1212 wants to merge 1 commit intoEswaramuthu:mainfrom
pradnya1212:improve-contact-ui

Conversation

@pradnya1212
Copy link
Copy Markdown

Which issue does this PR close?

  • Closes #.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Enhanced Contact Us section with improved styling, spacing, and hover effects.

Fixes #255

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 12, 2026

@pradnya1212 is attempting to deploy a commit to the 007's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown

Thanks for creating a PR for your Issue! ☺️

We'll review it as soon as possible.
In the meantime, please double-check the file changes and ensure that all commits are accurate.

If there are any unresolved review comments, feel free to resolve them. 🙌🏼

Comment thread static/styles.css
Comment on lines +781 to +800
/* ===== Contact UI Improvement ===== */

.contact-box {
background: linear-gradient(135deg, #2c3e50, #4ca1af);
padding: 30px;
border-radius: 12px;
color: white;
box-shadow: 0 6px 20px rgba(0,0,0,0.3);
margin-top: 20px;
}

.contact-box:hover {
transform: scale(1.02);
transition: 0.3s ease;
}

.contact-info ul li {
margin: 10px 0;
font-size: 16px;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correctness: The .contact-box, .contact-box:hover, and .contact-info ul li rules are placed inside the #scrollTopBtn declaration block — standard CSS does not support nesting like this, so all three new rule sets will be silently ignored by browsers that don't support the CSS Nesting spec.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In static/styles.css, lines 781-800 introduce new CSS rules (.contact-box, .contact-box:hover, .contact-info ul li) that are accidentally placed inside the #scrollTopBtn declaration block (before its closing brace). Move the closing brace of #scrollTopBtn to immediately after `transition: transform 0.4s ease;`, then place all three new rule sets after that closing brace so they are top-level CSS rules. This makes the styles valid and ensures they apply correctly in all browsers.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback! I will fix the CSS nesting issue and update the PR.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback! I will fix the CSS nesting issue and update the PR.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown


Confidence Score: 2/5 - Changes Needed

Not safe to merge — the CSS changes in static/styles.css contain a critical structural error where the .contact-box, .contact-box:hover, and .contact-info ul li rule sets are nested inside the #scrollTopBtn declaration block, which is invalid in standard CSS and will cause all three new rule sets to be silently ignored by most browsers. While the PR's intent to improve Contact UI styling is clear and well-scoped, the implementation will have zero visual effect in browsers that don't support the CSS Nesting spec (still limited adoption), meaning the feature is effectively broken for the majority of users. The fix is straightforward — the new rules need to be moved outside of #scrollTopBtn as top-level declarations — but the current state should not be merged as-is.

Key Findings:

  • .contact-box, .contact-box:hover, and .contact-info ul li rules are incorrectly nested inside the #scrollTopBtn block in static/styles.css; standard CSS does not support nesting, so these rules will be silently dropped by all non-nesting-aware browsers, rendering the entire UI improvement non-functional.
  • The failure mode is silent — no browser error is thrown, so this bug would not be caught by basic smoke testing and could ship unnoticed, leaving the contact UI unstyled despite the PR appearing to pass.
Files requiring special attention
  • static/styles.css

@pradnya1212
Copy link
Copy Markdown
Author

Hi, I have worked on this issue. Please review my PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve UI Quality of Contact Us Section

1 participant