Hi, I am using Sketch 57.1 with DSM. When importing a UI components from the DSM, I encountered a bud. In short, the text alignment changed from align in the middle to align to the top.
Here're the screenshots to demonstrate this problem:
1. I was trying to import the button components from DSM to my sketch.
2. Here's the setup for the button text: it should be horizontally and vertically aligned in the middle.
3. However, when I dragged the components to my sketch canvas: the alignment changed to align to the top and the new components imported from DSM has also alter my previous button component.
Can you help me to trouble shoot this problem? Thank you and I look forward to hearing from you.
comments
sort by
Hi Minshuo,
Thanks for taking the time to provide those screenshots to get a visual understanding of what's going wrong. So sorry to see that you're running into this issue with alignment.
It appears as if this may be related to a known issue that our Support and Engineering teams are working on. To determine if what you're experiencing is the same bug, our Support team will need to test directly with your file.
I will open a ticket on your behalf with our Support team so that they can take a closer look. Please keep an eye out for an email from one of our Support agents soon.
Thanks for hanging in there,
Shaina
If anyone else is experiencing this issue, please contact our Support team directly here including the following details:
I am having the same issue - is there any indication of when this might be fixed? It's currently breaking a significant portion of our design system.
If it helps to diagnose the problem, I'm pretty sure the bug is with the way that the DSM handles text styles. I noticed above that the OP has a style applied to the button text (best practice, as you advise). I have found that if i upload a component with no text style, the vertical alignment of the text remains intact.
This is a massive problem for our team as well. Is there any ETA at all on a fix?
Hi Tim and Ashley,
Sorry to hear that this is affecting you and your teams as well. I understand how frustrating it is to wait for a fix to an issue. The Engineering team is aware of the issue but we prioritize issues based on the scope and impact of the issue. For that reason, we don’t have an immediate fix or ETA available.
I would like to open tickets on each of your behalf so that our Support team can notify you as soon as there are any updates around this issue. Before passing this over to them, can you each please provide the following additional details?:
Look forward to hearing from you,
Shaina
Mac OS = 10.13.6
Craft 1.0.87
I would also encourage others to post here, as I'm guessing the bug detailed above must be affecting many other users. It will only be proiritised correctly if people make a noise about it. To my mind, it breaks the whole point of the DSM and makes uploading components futile, so should be treated as high priority.
Hi Tim,
Thanks for providing those details! I have spoken with the Support agents you are working with to notify them of your comments here in Community. They will be able to best assist you moving forward.
You're absolutely correct. The more reports we receive from users about issues like this helps our teams effectively prioritize issues based on their scope and impact. As soon as we have any updates about this issue, we will be sure to let you know.
Additionally, part of my job is to take important threads from Community to meetings with relevant Product Managers to discuss the struggles our customers are having. I will be sure to raise your concerns in my next meeting with the DSM Product Managers.
Thanks for hanging in there,
Shaina
I'm experiencing the same issue with alignment and colors changing. We're planning a DSM training session with our team within the next few weeks. Can I have an ETA?
Hi Rachel,
Thank you for taking the time to reach out about this issue. Sorry to hear that this is proving to be an issue with your upcoming training session with you and your team. So that we can keep you in the loop on this issue, I will be opening a ticket on your behalf with our Support team. Please keep an eye out for an email from one of our Support agents soon.
After working with some of the other users that have posted here, I can confirm that our Engineering team is aware of the issue. Unfortunately, we are unable to provide an update or ETA for a fix on this issue. However, I can assure that our team currently working to establish the root cause, and put a fix in place.
We are sorry that we can't provide a better answer at this time, and hope to have some good news soon! Please let me know if there's anything else I can help out with in the meantime.
Best,
Shaina