Skip to content

Settings and activity

3 results found

  1. 301 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    67 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Please note that stacks is a feature that is intended to be used at design time, and does not dynamically shift the stack in preview. I’m going to rewrite this particular request to be more precisely about the latter suggestion.

    An error occurred while saving the comment
    J Fox commented  · 

    Agree with this. Please change it. I am just trying to prototype some accordian lists on a content page. Because stacking is not respected when I make each accordian section it's own component with an expanded state, I made the entire content page a component that has stacking, with a separate state for each scenario when one of the accordian lists is expanded. However, now I run into an issue where the component seems to automatically switch it's y position when it is in different states. So, when clicking within the component to see the expanded state for one accordian, the whole component shifts upward on the page, covering the masthead. Maybe a separate and equally time consuming bug?

  2. 124 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    44 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    J Fox commented  · 

    I'm prototyping functionality in a web page design that expands or collapses a section of content under the header. I'm using a component state for the collapsed and then the expanded content section. It works great, except that my webpage artboard doesn't automatically resize to extend down to allow for the expanded section. So I basically have to start out with the collapsed sections with a really unecessarily long artboard/webpage, just so that when stakeholders try out the expand button, they will continue to see all of the content on the page.

  3. 260 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    J Fox commented  · 

    Yes - please add this. One major feature in the product I work on is expandable sections to condense information on content pages. I want to show the stakeholder how easy it is for users to click on a section heading and expand the section to see the contents, but to do that I need to be able to add a link from that section heading in one artboard to that same heading within the expanded view artboard. I sucks that I can't show this functionality to stakeholders.