-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unnecessary Back button on Order Lookup list page leads to incorrect navigation #785
Comments
please assign this project to me i will try to work on it. |
@Raj123-dev , please go ahead |
Fixed-Remove backbutton icon in OrderLookup.vue(#785)
The back button has been removed from the Order Lookup list page to address the issue of incorrect navigation. |
What does it mean??
…On Fri, 29 Nov, 2024, 12:09 pm Priyanshee Sisodiya, < ***@***.***> wrote:
The back button has been removed from the Order Lookup list page to
address the issue of incorrect navigation.
—
Reply to this email directly, view it on GitHub
<#785 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BAEIABXN6ZXAJENKHYNFU4T2DADZXAVCNFSM6AAAAABOZ3LXFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGE3TQNJQGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Apps testing is under process and thus its a validation comment that everything is working fine as expected, so nothing to worry about. |
Current behavior
The Back button is visible and, when clicked, it navigates the user to the 'open' tab/section.
Expected behavior
The Back button should not be visible on the Order Lookup list page, as there is no relevant previous page to return to within the Order Lookup flow.
Steps to reproduce the issue
Navigate to the Order Lookup tab, which opens the Order Lookup list page.
Observe the Back button visible on the page.
Click the Back button.
Environment details
App version : v2.9.1
App environment : UAT
Additional information
https://jam.dev/c/29e46557-0157-4397-9ebd-e9d1b5162c22
The text was updated successfully, but these errors were encountered: