Skip to content
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

Inconsistent use of 'pointer' cursor when hover to ENS or the contract address in Wallet and Executed Proposal page #68

Open
hafikraimy opened this issue Apr 16, 2023 · 5 comments
Labels
cbb Community bug bounty submission

Comments

@hafikraimy
Copy link

hafikraimy commented Apr 16, 2023

Steps to reproduce

  • Go over to the Proposal page by clicking the Proposal tab in the top navbar.
  • Click on any of the dao proposal's title in the API3 DAO Proposal list
  • In the Executed Proposal page, hover the cursor to any of the ENS or contract address in the list
  • The cursor does not become a pointer when hovered

Expected behavior

  • Mouse cursor on Executed Proposal and Wallet page should behave in same manner when the cursor hover to ENS or contract address.
  • The cursor should turn to 'pointer' cursor when user hover to any of the ENS or contract address on the Voting or Wallet page as to indicate that it is a link and clickable which will bring the user to the clicked address's wallet

What happened?

Screenshots (if applicable)

Screenshot of Executed Proposal page (cursor does not turn to pointer - defect)
Voting

Screenshot of Wallet page (cursor turn to pointer - expected)
Wallet

Environment

OS: windows 10 Pro
Browser: Chrome

Potential consequences

  • The cursor pointer is important as it indicates a link and help user to differentiate between a link and a normal text.
  • With this defect, user will get a different understanding and thought that the address or ENS is not a link and is unclickable. Hence, making the user confused on how to track back the vote caster's wallet.
@hafikraimy hafikraimy added the cbb Community bug bounty submission label Apr 16, 2023
@KenCarvAPI
Copy link

Hi @hafikraimy, we decided this was classified as feedback as opposed to a bug as such, but still a valid comment.

As such we were open to paying half the bounty (100 API3). Would you be able to share contact details for us to arrange transfer?

@hafikraimy
Copy link
Author

Hi @KenCarvAPI,

I appreciate your prompt response and assistance in arranging the transfer.
Discord ID: 359001461713141761
Discord username: hafikraimy#7548
Email: [email protected]

Let me know if there are any additional steps or information required to complete the transfer.

@hafikraimy
Copy link
Author

Hi @KenCarvAPI

Its been 3 weeks since the last update from your team regarding the bounty payout. I have shared my wallet address with Ben from you team. Is there a way you can speed this up ? or if you need any more details from me ?

@KenCarvAPI
Copy link

Hi @KenCarvAPI, apologies for the delay, I missed your email. Just made the transfer.

@hafikraimy
Copy link
Author

Hi @KenCarvAPI, appreciate for your fast reply. I have received the bounty. Thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cbb Community bug bounty submission
Projects
None yet
Development

No branches or pull requests

2 participants