From 87dcbedb80d661681c4b9cdf88bc7c6aa05508b5 Mon Sep 17 00:00:00 2001 From: CuriousX Date: Fri, 20 Sep 2024 13:00:18 -0600 Subject: [PATCH] Update src/registrar/assets/sass/_theme/_base.scss Co-authored-by: Rachid Mrad <107004823+rachidatecs@users.noreply.github.com> --- src/registrar/assets/sass/_theme/_base.scss | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/registrar/assets/sass/_theme/_base.scss b/src/registrar/assets/sass/_theme/_base.scss index 806261810..85f453dac 100644 --- a/src/registrar/assets/sass/_theme/_base.scss +++ b/src/registrar/assets/sass/_theme/_base.scss @@ -110,7 +110,7 @@ with the searchbar in widescreen mode. EXPLANATION: The existing frontend implementation puts the searchbar and export button in two separate columns in a grid, which creates a solid wrap-around effect -for mobile divices. The searchbar had a max-width that exactly equaled the max width +for mobile devices. The searchbar had a max-width that exactly equaled the max width of its parent column (for non-widescreens), so there wasn't any issue at this time of implementation. However, during immplementation of widescreen mode this small max-width caused the searchbar to