Scroll out of view

12:16:38 StoneCypher: GreenJello: when selecting browsers the scrolldown accomodates the new follow text, which is long enough to scroll browsers above the fold
12:16:39 GreenJello: I'm trying to decide if I should use the same UI for a fetch wrapper generator, or maybe something more conventional
12:16:52 StoneCypher: GreenJello: so you have to scroll back up to select your second browser
12:17:00 StoneCypher: again for your third, etc
12:17:51 GreenJello: StoneCypher, would you recommend removing the automatic scrolling, or prevent it specifically in response to the support buttons being clicked?
12:18:29 StoneCypher: depending on how much effort you want to put in, i'd keep the automatic scrolling but give it a distance limiter, so that the ui that triggered the initiating event cannot be scrolled offscreen
12:18:49 StoneCypher: the intent would be super clear to the user, and the ux would be doubleplusgood
12:19:18 StoneCypher: or rather, i guess the immediate container of the ui, instead
12:19:28 StoneCypher: so that the second row of browser buttons doesn't scroll the first row offscreen

Start by reproducing the browser-selection flow and inspecting where automatic scrolling occurs after support buttons are clicked. Done means selecting a second or third browser does not scroll the initiating control or its immediate container out of view, while the intended automatic scrolling remains usable.

Written by the indexing model from the issue text.