Optimize Footer Visibility in /history
Routes
#2598
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses an issue with the footer overlaying content in the
/history/***
tab, which detracts from the user experience by obscuring important information. To enhance usability and content visibility, we've implemented conditional logic to hide the footer on specific/history/***
routes that present detailed content.Changes Made
The main change involves modifying the
FooterComponent
to dynamically adjust its visibility based on the current route. Here's an overview of the code adjustments:Justification:
Given the /history tab's purpose to display detailed historical data and analyses, ensuring that this content is fully visible and unobstructed is crucial for user engagement and effectiveness of data presentation. This change directly contributes to improving the overall user experience by making adjustments based on the application's context and user needs.