UI Bug: Edit Form `Overflows` Screen on `Delete` Button Click

sophieturner0 commented 1 month ago

Describe the bug

When the Delete button is clicked within the Edit Form, the form overflows the bottom boundaries of the screen.

To Reproduce

Steps to reproduce the behavior:

Navigate to the Blueprint Modal.
Click on the "Person2" node.
Click the "Delete" button.
Observe that the edit form overflows the bottom of the modal.

Bug Demo:

https://www.loom.com/share/d552f202c5b1427ba41be816a899a46f

Bug Image:

Acceptance Criteria

[x] When the Delete button is clicked, the Edit Form should remain within the boundaries of the modal window, ensuring all form elements are visible and accessible without overflow.

sophieturner0 commented 1 month ago

Hi @tomsmith8, could you please review it and assign it to me?

MahtabBukhari commented 1 month ago

@tomsmith8 @AbdulWahab3181 @aliraza556 @kevkevinpal @Rassl We should come here in this platform with original profiles. A Developer always have a commit history on GitHub profile. It is impossible to become a developer without using GitHub. -> For making this platform free from fake profiles we should have to arrange video call meeting with open cameras. -> To Assign a bounty to a new hunter we should have to check the commit history and if possible arrange just 2min video call meeting with open camera.

We really need this action because original hunters are not getting works while fake ones getting all 🙏🙏🙏

aliraza556 commented 1 month ago

@tomsmith8 @AbdulWahab3181 @aliraza556 @kevkevinpal @Rassl We should come here in this platform with original profiles. A Developer always have a commit history on GitHub profile. It is impossible to become a developer without using GitHub. -> For making this platform free from fake profiles we should have to arrange video call meeting with open cameras. -> To Assign a bounty to a new hunter we should have to check the commit history and if possible arrange just 2min video call meeting with open camera.

We really need this action because original hunters are not getting works while fake ones getting all 🙏🙏🙏

Sure

AbdulWahab3181 commented 1 month ago

@tomsmith8 @AbdulWahab3181 @aliraza556 @kevkevinpal @Rassl We should come here in this platform with original profiles. A Developer always have a commit history on GitHub profile. It is impossible to become a developer without using GitHub. -> For making this platform free from fake profiles we should have to arrange video call meeting with open cameras. -> To Assign a bounty to a new hunter we should have to check the commit history and if possible arrange just 2min video call meeting with open camera.

We really need this action because original hunters are not getting works while fake ones getting all 🙏🙏🙏

I think it's really a good step, and I appreciate your efforts for this action. I just want to add two things. First, we should detect and remove existing profiles. Second, we should verify each profile via video call with a government document like an ID card, passport, or driving license. We can verify the identity automatically using the Veriff (https://www.veriff.com/) APIs in our existing application; otherwise, we have a manual calling process, depending on management's decision.

I also would like to mention @fvalentiner and @elraphty here so they can take the same actions in their repos.

tomsmith8 commented 1 month ago

Sphinx Chat and the Bounty platform uses permissionless technology that is privacy preserving by design. Therefore, there are no issues with users wanting to create multiple accounts for privacy reasons and we have no way to stop them, by design.

In order to incentivise bounty profiles, and reduce fake profiles we'll be adding reputation tracking soon where the workspace will sign off good work, fast PRs etc. so anyone with the highest history will benefit (disincentivising new accounts). So creating fake accounts just divide up the reputation.

stakwork / sphinx-nav-fiber