Skip to content
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

Made the form overflow instead of whole page #1404

Merged
merged 2 commits into from
Aug 26, 2022
Merged

Made the form overflow instead of whole page #1404

merged 2 commits into from
Aug 26, 2022

Conversation

MattKNichols
Copy link
Contributor

see issue: #1374

@github-actions
Copy link

@sonarcloud
Copy link

sonarcloud bot commented Aug 25, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link
Member

@sleidig sleidig left a comment

Choose a reason for hiding this comment

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

tested this in various screen sizes and it seems to work reliably. Thanks, this is a big UX improvement! 🎉

only on mobile there is a slight glitch - the component is still too long and scrolling to the very bottom, the title (name of beneficiary above the tabs) gets scrolled out. This is not a huge issue, though.

@@ -21,6 +21,9 @@ $max-screen-width: $min-block-width + $margin-main-view-right + $margin-main-vie
.columns-wrapper {
@include adaptive-grid($min-block-width, $max-screen-width);
align-items: start;
position: relative;
height: calc(100vh - 240px);
Copy link
Member

Choose a reason for hiding this comment

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

because the 240px depend on the space taken up by our heading of the view above, this will stop working (i.e. start showing a second scroll bar) when we change things about other components outside of this.

The idea of CSS certainly is to lay out things well stacked and use relative measures ... but with all our components inside each other this is a huge pain in the a**. So let's go with this for now 😉

Copy link
Member

Choose a reason for hiding this comment

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

@Schottkyc137 should we consider reworking things from the root inwards, so that the overall views always exactly fill the screen and inside components like this one take up relative space and display their own scrolling?

Copy link
Contributor

Choose a reason for hiding this comment

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

@Schottkyc137 should we consider reworking things from the root inwards, so that the overall views always exactly fill the screen and inside components like this one take up relative space and display their own scrolling?

At some point, I think that this is the way to go. That being said, our large HTML tree certainly complicates this (because a lot of elements need to have their height set appropriately) but in the end, it might be worth it.

@TheSlimvReal TheSlimvReal merged commit c198d07 into master Aug 26, 2022
@TheSlimvReal TheSlimvReal deleted the form-ux branch August 26, 2022 09:40
@aam-digital-ci
Copy link
Collaborator

🎉 This PR is included in version 3.9.1-master.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@aam-digital-ci
Copy link
Collaborator

🎉 This PR is included in version 3.9.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants