Skip to content

fix: preview mode navigation previous button (that uses legacy UI) - #31193

Merged
Agrendalath merged 1 commit into
openedx:masterfrom
open-craft:navin/fix-preview-mode-navigation
Oct 25, 2022
Merged

fix: preview mode navigation previous button (that uses legacy UI)#31193
Agrendalath merged 1 commit into
openedx:masterfrom
open-craft:navin/fix-preview-mode-navigation

Conversation

@navinkarkera

@navinkarkera navinkarkera commented Oct 21, 2022

Copy link
Copy Markdown
Contributor

Description

Makes Previous and Next button in lms preview mode consistent, i.e.

  • clicking on next button takes you to next chapter if there are any chapters left in current subsection else takes you to first chapter
    of next subsection
  • clicking on previous button takes you to previous chapter if there are any chapters present before the current chapter in current subsection else takes you to the last chapter of the previous subsection.

Previous button should use prev_url if it in first position. In studio UI, it should always use prev_url. To make this possible we checking length of contents which is always zero for studio and more than 0 for legacy UI.

Supporting information

Private ref: Jira: BB-6820

Sandbox

Testing instructions

  • Test next and previous buttons in lms preview mode.

Legacy UI: Previous button should use prev_url if it in first
position. In studio UI, it should always use prev_url. To make this
possible we checking length of contents which is always zero for studio
and more than 0 for legacy UI.
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @navinkarkera! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

  • supporting documentation
  • Open edX discussion forum threads
  • timeline information ("this must be merged by XX date", and why that is)
  • partner information ("this is a course on edx.org")
  • any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

@Agrendalath Agrendalath left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

👍

  • I tested this: checked navigation in the Preview
  • I read through the code
  • I checked for accessibility issues: n/a
  • Includes documentation: n/a
  • I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository: n/a

@Agrendalath Agrendalath self-assigned this Oct 25, 2022
@Agrendalath
Agrendalath merged commit a959c5d into openedx:master Oct 25, 2022
@Agrendalath
Agrendalath deleted the navin/fix-preview-mode-navigation branch October 25, 2022 15:23
@openedx-webhooks

Copy link
Copy Markdown

@navinkarkera 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

EdX Release Notice: This PR has been deployed to the production environment.

@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

EdX Release Notice: This PR has been deployed to the production environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants