razorpay / razorpay/razorpay-node

Multiple Frontend Issues Affecting User Interactivity and Experience

Open
#419 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
243
Forks
129
PR merge metrics
No merged PRs in 30d

Description

Steps to reproduce the behavior
  1. Navigation Bar Hover Overlap
  2. Incomplete Product Information in Cards
  3. Oversized Login Interface
  4. Slow Loading of Pricing Page .
Expected behavior
  1. The navigation bar should highlight smoothly without overlapping with the container content.
  2. Each product card should display complete and detailed information about the product.
  3. The login interface should be resized to a user-friendly dimension and include clear authentication prompts.
  4. The pricing page should load quickly and efficiently, providing immediate access to pricing information.
Actual behavior

Changes the navigate bar hover which overlap with container it would not make a user interactivity ,
Second section of website there are multiple card present but they actually does not show the complete content about product. And when user go for login then the UI interface is too big(container) where I have not seen the proper authentication for user friendly , I think it might little changes there .
And when I go for price navigate bar it takes lot time to load the actual content of it.

Code snippets

No response

Node version

v21.7.2

Library version

v2.9.4

Additional Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names navigation hover, product cards, login UI, and pricing-page loading, but provides no files, tests, or entry points. First verify that these frontend concerns belong in this Node.js bindings repository, then split them into focused issues with reproducible cases. Done should be defined separately for each issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
frontend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.