Full screen viewing of web prototypes (responsive) does not allow fix position elements, why?

Hi there,

First of all I would like to say that I truly appreciate the latest update version 12.0.12.10.

But I have to say that some things are confusing me. So far I've figured out that in order to have the prototypes in full screen and responsive one needs to either match the "viewport height" to the height of the composition you've been working on or completely remove vertical scrolling. Is that how it is supposed to work?

I'm guessing the answer is yes given that the explanation in the update page reads as follows: "If you have defined the viewport height (set in the Property Inspector), the prototype fits to the height first and proportionally scales width to maintain the aspect ratio. You can also scroll vertically to view content that is below the viewport height."

Because if that is the case I must say that this logic is rather counter intuitive and also has some pretty negative side effects. The main one, and very important, is that elements which are marked as "fix position when scrolling", stop being fixed completely. Is this supposed to happen or am I going completely the wrong way about this?

On a more general note I would like to express that from my point of view the engineering philosophy behind defining a "viewport height" seems to be what was has been creating big problems for this tool. I understand that it makes sense from an engineering stand point but from an UX perspective that doesn't seem to make much sense, let me explain why. If you select a viewport that implies that you know the target viewport you'll be using, that might be true for in-house user testing (when you know the machine specs you'll be using) but its not true for remote user testing (where a pool of users can have any device type and access the prototype), which, both, are my case. That basically renders the prototyping aspect of Adobe XD useless and that is why I have to resource to other prototyping tools to issue the prototypes to users. I would really appreciate if someone could address this aspect of the tool given that I would be more then happy to use the prototyping aspect, which I simply can't currently.

I thought this responsive update would literally tackle this aspect of the tool but in effect it did very little on the prototyping side but improve greatly the design side of the tool. I would really appreciate if you would take in consideration the use case of Designers that have to do remote user testing and cannot know the target device height or width.

I apologise for the long text but it was necessary to describe in depth the issue.

Once again thank you very much for the update, the time and the effort you folks put into this tool. It's greatly appreciated!