Basically do it like invisionapp does it. go ahead and implement a number of other great features they have that XD currently does not, like ability to prototype to objects and not just artboards.

I'd really like to know how people are currently working around this? It makes prototyping basically unusable when adding micro interactions, specially in mobile. Setting the scrolling to none is not really feasible as well.

Yes, add this ASAP

I honestly cannot wait for this! I still use InVision just because XD doesn't offer this feature, yet. Can't wait until it updates :)

I made a button on my website in Adobe XD. When it's below the fold and i click on the button my website always go's back to the top. I want the view to stay on the same point so you can show a different state.

With prototyping wizzards it's really enoying the view go's back to the top. I want to show people the next step without scrolling. Now you have to scroll through the steps you've already made.

Please! We need this.

I have found users get very confused during my tests when the page keeps scrolling to the top instead of adding to the area they clicked. It ruins the illusion of testing a "real" product. I will unfortunately have to go back to InVision until this is implemented.

I'd like to be able to set a viewport starting position on an artboard. For instance. I have a design I'm working on in which I click a button and a search filter box opens to achieve this I have to create the filter box in a different artboard, however when I do this and click in preview mode it starts at the top of the page, breaking up the flow of my preview.

So in short if I could select where the viewport starts on the page I'd be able to set up previews for more interactive elements.

Switched over to XD and its great, but theres a few prototyping issues like this that keep me going back to InVision.

XD definitely needs it. I love the ease of use and speed to work with XD, but it's unprofessional when presenting prototypes to clients. "Oh, no it won't do that on the real thing. No."

Inivsion calls it " Maintain scroll position after click"

Without a short-term fix (we don't need to wait for an all-singing layers/reveal thing) this problem basically makes it useless for prototyping anything below the fold. 'Stitching in' in-between screens isn't really a viable option I don't think.

When moving from one screen to another by clicking a button it would be great if we could set the scroll position fixed. This is very helpful in interaction design. For example opening the view more content, selecting options, payment methods etc.

Currently moving from one page to another throws use at the top of the next page and user has to scroll to the needed point.

This needs to be fixed short term because it completely blocks out any possibilities to simulate an experience that's outside of the fold.

Completely agree with the below comments: when you're designing a long screen with a lot of interaction (like a filter screen for example), every time someone clicks on a clickable element, they are directed to the right screen – but all the way to the top of that page. So the feedback of their action isn't clear (they have to scroll to see the new state of the element) which means they don't experience the interaction as it is designed. Would highly appreciate adding this feature!

When you prototype a button, you can only send to another artboard, and not to a specific area from that artboard. So if you are at the end of your artboard and click a button just to change a picture, you go to other artboard from the begging and need to scroll to the end again.

For example: When I'm on a long page and want to click on a checkbox or radio button halfway down the page, it would be awesome if the target artboard could be at the same scroll point, in stead of at the top of the page.

Maybe there could be an extra drop down when linking. Under target. Scroll to: "top of target" or "same croll position".

Emanuele. Thank you for the suggestion. Longer-term, we want to create symbols and states, so that you can simply show hover / selected states for buttons, without creating entirely new artboards. Would this suit your use-case?

In the short term, you could work around this by stitching in a non-scrolling artboard to demonstrate this state change.

Regardless, I will communicate this to product management, and we will continue to watch as more votes come in.

This would be huge. Basic function to compete with Invision.

@PeterFlynn I want the scroll position of a 2nd artboard to match the scroll position of the artboard you just came from. This is necessary to simulate all in-place interactions (i.e. think about a switch button changing color when clicked).

Just to clarify -- are you looking to preserve the scroll position when you return to an artboard you've already been to? Or do you want the scroll position of a 2nd artboard to match the scroll position of the other artboard you just came from? (Assuming their heights are similar enough)