Users reported that during signup, it’s not obvious they need to scroll down to complete required fields, especially on macOS and iOS where scrollbars are hidden. tkrunning and evantill shared screenshots showing the issue, noting users couldn’t proceed because hidden fields weren’t visible. awesomerobot suggested increasing the modal height via CSS (max-height: 70vh), which helped but caused layout issues on iPhone 6 Plus evantill. codinghorror emphasized OS/browser variability in scrollbar visibility. The team explored two solutions: forcing scrollbars to appear or changing the “Create New Account” button to always be clickable, scrolling users to the first incomplete field. sam preferred the latter, citing success with similar changes in the composer. vinothkannans implemented the fix in a PR, now merged, which also improved error messaging by using “enter” instead of “supply” and removed unnecessary margins. cybe requested visual cues like red highlighting for missing fields, noting ongoing user frustration. The fix aims to make signup more intuitive without relying on scrollbars.
I received some very valid feedback today from a user. I’m not sure if there’s already a good way of dealing with this issue or not. If not, I’d say it’s something worth thinking about how to improve.
But after all visible fields were completed, it wasn’t immediately clear that the user would have to scroll down to find the final required field/checkbox:
Sure, there’s some slight fading of the content, but that’s not very obvious for most people.
I’m not sure what the best approach would be to improve this—perhaps a visual hint that scrolling is needed? Or simply expanding the signup modal so all fields are visible?
And is there something I can do immediately that would improve the signup flow for my users?
You can make a minor CSS adjustment to allow the modal to get taller on desktop devices, this should do it:
.d-modal.create-account .login-form form {
max-height: 70vh
}
At the moment our default max-height is more restrictive, I can probably allow it to get a little taller by default… but there’s always going to be a point where the scroll cut-off isn’t obvious for someone with X number custom fields added. I really hate that macOS does this hidden scrollbar behavior.
Thanks @awesomerobot, I’ll give that a try! (I assume you meant max-height: 70vh; which seems to work perfectly!)
And I do appreciate that this primarily an issue on MacOS, @codinghorror. However, 1/3 of my desktop users are on MacOS, so it’s not an insignificant part of my audience.
I recommend overriding CSS on your instance to make it clearer – as stated above, many operating systems suppress scrollbars heavily so I guess I’ll just quote myself..
Solving this is tricky because most touch devices hide scrollbars by default, our signup form is in a modal, the signup form length can vary if additional fields are added, and browser heights vary.
Outside of the extra-large change of moving the signup form to a full page instead of a modal… I think there are a couple possible solutions and one (or both) could probably improve things:
In modern browsers we can force scrollbar appearance with CSS. This means it will always be visible on touch devices (so scroll is more obvious). But this also means we’re overriding the default OS scrollbar styles on the signup modal, so it may look out of place.
We can change the behavior of the “Create New Account” button. Instead of disabling it until the form is complete, we can allow people to click it, and then scroll them to the first incomplete input.
Forcing scrollbar appearance should be simple to try out first, @codinghorror/@sam do you have any feelings about it?
I really like this solution best, @vinothkannans can you take it?
We had the same issue on the composer for years and changing it to always clickable erased a large amount of issues, the bouncy red animation really tied stuff up on the composer.
This looks good, I think it should be a lot more obvious now!
I added an additional change that removed a margin and uses “enter” instead of “supply” in the required messages (we use “enter” in the validation messages, so I copied that).