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
There seems to be a problem with navigating between tabs within the Release Coordinator page when accessed from a mobile device. Specifically, one cannot move to other tabs such as “MISC” or “FEATURES” due to the absence of navigation options in the mobile viewport.
Important TODO:
Please note that there is a test currently skipped on mobile viewports due to this navigation issue. The “MISC” tab, which is inaccessible, is essential for testing promo messages. Once this navigation problem is resolved, the corresponding code that skips this test on mobile viewports should be removed. Make sure to do that as a part of PR fixing this issue.
i) Access the Release Coordinator (/release-coordinator) tab on Oppia from a mobile device or at mobile viewport
ii) Attempt to navigate to the “MISC” or “FEATURES” tabs.
Expected Behavior
Users should be able to seamlessly navigate between all available tabs within the Release Coordinator page, regardless of the device or viewport. Navigation options should be clearly visible and functional in the mobile viewport.
Screenshots/Videos
What device are you using?
Desktop
Operating System
MacOS
What browsers are you seeing the problem on?
Edge
Browser version
No response
Additional context
No response
Tips for developers
Before addressing the bug, please identify which PR caused the issue (you can follow the steps here). If you identify the PR, comment on the issue with a link to it. If not, mention the commit hash of the oldest commit you saw the bug on (and the month and year it was made in).
Then, please leave a comment with details of the approach that you plan to take to fix the issue (see example).
Note: If this is your first Oppia issue, please make sure to follow our guidelines for choosing an issue and setting things up. You will also need to show a demo of the fix working correctly on your local machine. Thanks!
The text was updated successfully, but these errors were encountered:
Hi @Akhilesh-max, a fix is included in #20439 by modifying the release coordinator navbar component to have navigation similar to the admin page. It should be merged very soon but please feel free to take a look in case you are being blocked.
Thanks for taking a look, @Vir-8.
Yes, a mobile test is blocked onto this due to the lack of navigation in the mobile viewport.
Do you feel, your fix could be merged by tomorrow, EOD?
Describe the bug
There seems to be a problem with navigating between tabs within the Release Coordinator page when accessed from a mobile device. Specifically, one cannot move to other tabs such as “MISC” or “FEATURES” due to the absence of navigation options in the mobile viewport.
Important TODO:
Please note that there is a test currently skipped on mobile viewports due to this navigation issue. The “MISC” tab, which is inaccessible, is essential for testing promo messages. Once this navigation problem is resolved, the corresponding code that skips this test on mobile viewports should be removed. Make sure to do that as a part of PR fixing this issue.
URL of the page where the issue is observed.
http://localhost:8181/release-coordinator
Steps To Reproduce
i) Access the Release Coordinator (/release-coordinator) tab on Oppia from a mobile device or at mobile viewport
ii) Attempt to navigate to the “MISC” or “FEATURES” tabs.
Expected Behavior
Users should be able to seamlessly navigate between all available tabs within the Release Coordinator page, regardless of the device or viewport. Navigation options should be clearly visible and functional in the mobile viewport.
Screenshots/Videos
What device are you using?
Desktop
Operating System
MacOS
What browsers are you seeing the problem on?
Edge
Browser version
No response
Additional context
No response
Tips for developers
Before addressing the bug, please identify which PR caused the issue (you can follow the steps here). If you identify the PR, comment on the issue with a link to it. If not, mention the commit hash of the oldest commit you saw the bug on (and the month and year it was made in).
Then, please leave a comment with details of the approach that you plan to take to fix the issue (see example).
Note: If this is your first Oppia issue, please make sure to follow our guidelines for choosing an issue and setting things up. You will also need to show a demo of the fix working correctly on your local machine. Thanks!
The text was updated successfully, but these errors were encountered: