You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
As an organizer, while in the "Proposed" or "In Progress" sections of Missions Control, if I click on a drop down box for a mission towards the bottom of the screen, the drop down opens in place, while the mission card is scrolled to the top and focused. Clicking on the drop down again, or clicking on the drop down where it opens initially, still functionally works.
Steps to Reproduce (this example uses the "In Progress" page):
Log in as an organizer.
Navigate to either "Proposed Missions" page, or the "In Progress" page (in this example, I go to the "In Progress" page).
Click on the drop down box for any mission.
Expected Behavior:
Drop down box will open, connected to the associated mission card.
Actual Behavior:
Drop down box opens in place, while the mission card "focuses" to the top of the screen, causing the drop down to become disconnected from the card.
Notes:
Tested on Firefox and Chrome desktop with same behavior.
The text was updated successfully, but these errors were encountered:
Description:
As an organizer, while in the "Proposed" or "In Progress" sections of Missions Control, if I click on a drop down box for a mission towards the bottom of the screen, the drop down opens in place, while the mission card is scrolled to the top and focused. Clicking on the drop down again, or clicking on the drop down where it opens initially, still functionally works.
Steps to Reproduce (this example uses the "In Progress" page):
Expected Behavior:
Drop down box will open, connected to the associated mission card.
Actual Behavior:
Drop down box opens in place, while the mission card "focuses" to the top of the screen, causing the drop down to become disconnected from the card.
Notes:
Tested on Firefox and Chrome desktop with same behavior.
The text was updated successfully, but these errors were encountered: