Copy link to clipboard
Copied
The hover state of a component is set up fine on the art board (the text is supposed to be bold in hover state), but when I preview it only the default state shows. It's actually my student's project -- we're playing around with Xd in my web design class. I'm not an expert in Xd, but thought it'd be nice to try it for wireframing.
I'm using version 44.1.12 on a macbook pro (13-inch, 2017, 2.3 GHz Intel Core i5), but she created it in the newest version of Xd on a PC.
Here is a video: https://youtu.be/f82rKtnJeOw
Here is a link to view it in design review.
Here is a link to view it in deveolpment mode.
Any help is much appreciated! We just like to be able to see the hover state after pressing the preview button.
1 Correct answer
Just took a look at the file, going to describe the different issues and how to fix them.
1. For the hover effect, for some reason there was no hover interaction, as I suspected. The "Hover State" is just like any other state, with the difference that it has a hover interaction applied by default to the default state, but you must have deleted it by accident for some reason.
Instead, it should be like that:
You can add it by either clicking on the blue arrow on the component, or on t
...Copy link to clipboard
Copied
Hey there! Both of the links you placed there point to this thread and not to the prototype 🙂
And along with reposting the correct links, would you mind uploading the .xd file with just that artboard, so we can inspect it? If you can't share the file, post the same screenshots, but from the prototype tab, so we can see what interactions are added.
What I suspect is happening - you have replaced the default hover interaction that gets attached when you add a hover state with a transition to another artboard instead. Usually the transition interaction is added to the hover state, and not to the default state. Technically you can add both a tap and a hover on the default state, but it doesn't work very well. It can be tricky and confusing if you haven't done enough mistakes with it 🙂
Copy link to clipboard
Copied
Thanks so much. I appreciate that you've already taken the time to respond!
I'm not sure why the links lead back to the thread....
But I've uploaded are two files (one with just the home page and the other with multiple pages w some interactions). But the files are much larger on my local computer than what seems to be uploaded here, so perhaps I did something wrong.
We do have interactions on the original document so that one should be able to hover over the menu item component (the font should turn bold) as well tap on it to take the user to another page.
Hopefully this time it will work -- here is a link to view it in design mode:
And hopefully a link to view it in development mode:
https://xd.adobe.com/view/fa1a10eb-d580-44a6-a2f7-42da08ba3ceb-af49/
I'm happy to add anything elseya'll need to look at ao that you can try to help me understand what's going wrong. Incidentally I do the same thing on my personal prototype and it works fine. This one was built by my student and I just can't figure out why it isn't behaving the same as mine.
Copy link to clipboard
Copied
Itt would n't upload my files to here directly so I've put them in a dropbox folder:
https://www.dropbox.com/sh/8zk5cnobnh6sl27/AACyK8ftAUBgTWeATwT0INRga?dl=0
Copy link to clipboard
Copied
Just took a look at the file, going to describe the different issues and how to fix them.
1. For the hover effect, for some reason there was no hover interaction, as I suspected. The "Hover State" is just like any other state, with the difference that it has a hover interaction applied by default to the default state, but you must have deleted it by accident for some reason.
Instead, it should be like that:
You can add it by either clicking on the blue arrow on the component, or on the + icon in the Interaction tab on the right, and set the interaction to hover. The destination should be the hover state.
For the transition to a different page from that same button, you can do 2 things:
- Add a second interaction with "Tap" to the default state, that will point to a different page.
- Add the transition to the hover state.
I also prefer to remove the animation on the hover state, unless necessary, since Xd waits for the small transition to finish before letting you click on the menu item, which feels disruptive. Instead of Auto-Animate I use Transition, and set the animation to None for hover states.
2. Setting up the menu: The proper way to prototype the menu is to make it a component on a separate artboard on its own, and create the links to all the pages. Then add it as a component to each page, so you won't have to redo the wiring for each page, since a menu item can't point to it's own page. This way you will see on each page only the link to itself is gone, while the rest are working fine.
Also, on each page, you switch the current page item to its hover (active state).
3. Menu item components: Instead of a pseudo rectangle behind the element to mark the clickable area, use padding on the component. I also prefer to center the text and use auto-width for the text elements, which avoids some weird displacement happening between states and different text.
4. Viewport height: I noticed you have different viewport heights on the lower pages, which creates some weird re-framing in the prototype, you should aim to make them all the same.
I've fixed all these for you, so you can see how I would set it up. Here's the file.
Copy link to clipboard
Copied
You are incredibly kind and helpful. Thank you so much. Reading your comment makes sense to me and I see how it would be better to create the menu component on its own. Seems so logical, but I hadn't thought of it. As soon as I'm done teaching I'll be looking over the rest of your instructions and examing the new artboard to make sure I understand. Again, I really appreciate your response -- I really am wanting to learn/understand Xd better and you helped me to do that.
Copy link to clipboard
Copied
Hi,
I've followed this thread and applied the changes, but the hover state still doesn't work in preview mode.
Is there anything else that I could try to fix it?
Thanks
Rachel

