-
Notifications
You must be signed in to change notification settings - Fork 214
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
resolved issue #756 #766
resolved issue #756 #766
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for collect-your-gamingtools ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, @wareeshaali2003! 🎉 Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project.
We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines
Hi there! This issue is still open. We are looking forward to your response. |
1 similar comment
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
20 similar comments
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
16 similar comments
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Hi there! This issue is still open. We are looking forward to your response. |
Pull Request Format
PR Title
Issue #756 : Overlap of Scrollup and chatbot icons solved
Type of PR
Add X in the box to specify the improvement type.
Bug fixed
Description
This pull request aims to fix a UI bug where the scroll-up button overlapped with the chatbot icon. The solution involved adjusting the CSS positioning of the .scroll-top button to improve visibility and prevent overlap.
Screenshots / Videos (if applicable)
Before:
-The scroll-up button positioned at 5% created an overlap with the chatbot icon, causing usability issues.
After:
Checklist
Additional Context
The main challenge was positioning the .scroll-top button so that it remains visible on the screen without overlapping with other UI elements like the chatbot icon. Adjusting the position from 5% to 6% proved effective in resolving this issue.
Thank you for reviewing my pull request!