fix(o3-5297): keep Vitals & Biometrics Add (+) button visible when right drawer is open #2917
+118
−4
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.
Requirements
This PR has a title that briefly describes the work done including the ticket number and follows the conventional commit format.
My work is based on existing Patient Chart and Vitals & Biometrics UI behavior and follows the O3 style guide.
My work was manually validated using existing application behavior across different screen sizes.
Summary
This PR fixes a UI issue where the primary “Add” (+) action in the Vitals & Biometrics section becomes partially hidden when the “Start a visit” right-side drawer is opened on the Patient Chart.
When the drawer opens, the main content area shrinks but does not correctly reflow its contents, causing the primary action button to be clipped.
This change ensures the main content resizes properly and keeps the primary action fully visible and accessible even when the right-side drawer is open.
Screenshots
Before:

After:


Related Issue
O3-5297
Other
Improves usability and discoverability of a primary clinical action
Prevents user confusion, especially on smaller screens and laptops
Aligns Patient Chart layout behavior with responsive UI best practices