Why do my components' scroll behavior "Position" always reset to "Scroll with parent"?

Ask the community
, ,
1

Is this just the default behavior of components when put inside a frame?

Example, I created a navbar component and have it’s Scroll Behavior - Position set to “Fixed.” When I drag it from the assets panel the Scroll Behavior will reset to “Scroll with parent”. The component does not keep the “Fixed” setting… I know I can just copy and paste to preserve that setting…but it makes workflows slower because I have to find my style sheet and copy the main component every time I make a new frame for a different screen.

Thanks for any answer.

3

Hey @Kenny_Xiong, sorry to hear this is happening!

It’s hard to understand and be sure what’s happening without seeing your file.

Are you able to provide a link so that we here in the community can take a closer look and try to reproduce?

4

Sure, I’ll share a link and some images. I’m just trying to update my portfolio with a small number of screens, but for larger projects it might cause some confusion.

Shared with view only, I won’t mind opening it for editing.
Link to my project

My navbar component has a it’s scroll Position set to “Fixed.”

navbar-component
navbar-component763×363 20.5 KB

If I copy and paste the main component from a sticker sheet, it keeps its position.
navbar-fixed-OK

Navbar component in the assets panel won’t retain a fixed position.

navbar-in-assets-panel
navbar-in-assets-panel953×482 40.5 KB

After inserting an instance of the component, the position is reset to “Scroll with parent.”

navbar-scrollwithparent.
navbar-scrollwithparent.762×670 35 KB

5

Thanks, @Kenny_Xiong!

We’ll pass this along to our prototyping team to investigate.

6

Thanks for your reply! Sounds good.

8

Hey @Kenny_Xiong, so sorry for the delayed reply!

I went OOO on January 31st.

We’re not able to see the exact naming of your components with View only access, but please try this workaround. Issues with scroll behavior are usually related to the limitations with the new State management for prototypes .

For most users, this issue is caused when objects do not share matching names. In order to share a scroll state, they need to have matching names according to this rule.