Component States to Development (Design Specs)
How can we export Hover states to development?
In the specs there is only one state in the component. How will development see all states?
Yifat
shared this idea
14 comments
-
Matt Brett
commented
Indeed, the lack of hover states in development mode is currently the only thing that's forcing me to export assets manually for developers.
-
Inc Beats
commented
Without development this feature is just a pain
-
Serkan Zararsız
commented
Here is a screenshot what developers need to implement the designs correctly!
We really hope this is included in the next update!Best,
Serkan Zararsiz -
Gin Arrufat
commented
The interaction between states should be available in all documents a source file is linked. It's a pain to have to reanimate the interaction of a component when it's used outside the source.
-
Cathi Swanson
commented
@thomas O - Howard Pinsky said in his livecast yesterday this feature was in development. Really hoping he is right, as "backlog" does sound bad...
-
Thomas O
commented
Feature in the backlog sounds like it's NOT a priority
-
Thomas O
commented
Ummm, yeah Adobe. Hover effects are fun but it's useless if devs can't get the CSS specs of all transitions and states. Please fix this is next update so we can actually USE the new features in our workflow and not just play with them.
-
Hover not working in the prototype link is a bug and we are looking into it on priority. Sorry for you to have encountered this and we will address it shortly.
Thanks! -
Stefanija Naskova
commented
As I saw in other requests, yes, we need the hover states to be shown in the design specs, when sharing with developers, but also it would be SUPER useful to see the hover states in shared for design review links.
I'm writing this after I spent some time designing the hover states interactions and excited to show them to the Product Manager, only to disappoint both of us.
-
Michael Laugesen
commented
Agree, i've spent hours making my design with component states, just to find out my developer can't incpect the individual states.
Please add a "state selector" with reference to the individual states defined when designing.
-
Cathi Swanson
commented
The lack of design specs regarding component states is a HUGE MISS. Sure, my prototypes will look hella cool, but I still have to detail out every.single.state separately for my developers.
-
Anonymous commented
in the development share more, where can I see the component states? for example hover effect, doesn't display the hover status color on css, only default.
https://xd.adobe.com/view/d74d6593-e162-43b6-7ce2-50360e719eea-a17c/
-
Anonymous
commented
On November 4, 2019 update new feature called "component states" introduced !! very helpful feature !! But the layers which were marked as "Batch for export" was not visible in development link, Please fix it ASAP, then only this feature will be useful for developers
-
Anonymous
commented
great new hover effects with the implementation of component states! but i guess we need the hover values in the design specs, otherwise the devs won't integrate the hover effects...
