Skip to content

Conversation

@YashK2005
Copy link
Collaborator

Small fix for dropdown styling where some dropdowns in the intake form were being covered.

Before
image
After
Screenshot 2025-11-10 at 7 41 39 PM

Notion ticket link

Ticket Name

Implementation description

Steps to test

What should reviewers focus on?

Checklist

  • My PR name is descriptive and in imperative tense
  • My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
  • I have run the appropriate linter(s)
  • I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

Copy link
Collaborator

@chene0 chene0 left a comment

Choose a reason for hiding this comment

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

lgtm

@YashK2005 YashK2005 merged commit 2f8be8a into main Nov 11, 2025
1 check passed
@YashK2005 YashK2005 deleted the fix/dropdown-z-index branch November 11, 2025 02:18
UmairHundekar pushed a commit that referenced this pull request Nov 25, 2025
Small fix for dropdown styling where some dropdowns in the intake form
were being covered.

Before
<img width="421" height="341" alt="image"
src="https://github.com/user-attachments/assets/85a5dc4f-0e0f-4df6-a061-cb7ed202eb50"
/>
After
<img width="472" height="475" alt="Screenshot 2025-11-10 at 7 41 39 PM"
src="https://github.com/user-attachments/assets/8e7f3e67-eda9-4a06-8f7b-b0db418cf8a0"
/>

## Notion ticket link
<!-- Please replace with your ticket's URL -->
[Ticket
Name](https://www.notion.so/uwblueprintexecs/Task-Board-db95cd7b93f245f78ee85e3a8a6a316d)


<!-- Give a quick summary of the implementation details, provide design
justifications if necessary -->
## Implementation description
* 


<!-- What should the reviewer do to verify your changes? Describe
expected results and include screenshots when appropriate -->
## Steps to test
1.


<!-- Draw attention to the substantial parts of your PR or anything
you'd like a second opinion on -->
## What should reviewers focus on?
* 


## Checklist
- [ ] My PR name is descriptive and in imperative tense
- [ ] My commit messages are descriptive and in imperative tense. My
commits are atomic and trivial commits are squashed or fixup'd into
non-trivial commits
- [ ] I have run the appropriate linter(s)
- [ ] I have requested a review from the PL, as well as other devs who
have background knowledge on this PR or who will be building on top of
this 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.

2 participants