Currently, when you select turn on "Responsive Resize", then "Manual", selecting "Fixed to [Direction]" the element is only fixed to that direction until the opposing direction touches the element, for which the element is now pushed by that opposing direction and no longer Fixed to the Original Direction you set initially.

Current behavior: If element is 100-pixels from the left and it is fixed to the left, dragging the artboard from right-to-left will keep the element locked to left UNTIL the right edge touches the element and pushes it out of the left of the artboard. Overriding the "Fixed to Left" parameter that was set.

Expected behavior: If the element is 100-pixels from the left and it is fixed to that, it should always be 100-pixels from the left, even if the right outer bounds of the artboard is pushed up against it. It should cut off on the right edge of the artboard and not the left since the left was initially locked to that.

Thank guys!

Expected behaviour:
When you create a new component the coordinates of any object inside that component have to be relative to the component anchor point (top left) since constraints are relative.

Actual behaviour:
The coordinates of any object inside a component are relative to the artboard which makes the data inconsistent with constraints.

Use cases, problems and implications:
- Impossible to create consistent padding\margins across multiple components.
- Impossible to maintain and check the spacing, paddings and margins across new elements in the design system (for ex. created by junior/mid designers)
- Impossible to automate design testing during dev ops handoff phase

Solution:
Make coordinates relative to the parent components' anchor point.

I'm reopening this issue because in the last one, I wrote two issues, not just one, and it was removed because "What you’re describing is a workflow that is the case when using magic mouse. The workaround is unfortunately, not to use the mouse". I think that answer was for the second issue, not the first.

To rephrase the issue: When I drag an item around the canvas (not necessarily to the edges of the window), I keep the LMB of my Magic Mouse down. But while moving the mouse, keeping the LMB pressed down, I probably rotate the tip of my finger a bit on the sensitive area of the mouse, which results in panning of the canvas. Please disable panning while dragging items.

I don't think it is a 'workflow' issue. It is an issue where two functions (panning and dragging) are allowed to execute at the same time. I can think of no situation where this is wanted behaviour. It also happens in other Adobe apps, but also in Sketch and Apple apps. However, in XD the bug is the most obvious, because the scrolling/panning is totally different from other apps. Much more (or even too) sensitive.

I think Adobe has the power to fix this issue with a software update. "Not using the Magic Mouse, cheers" is not really an answer. Everyone gets one if they buy an iMac. Forcing every iMac && XD user to switch to another mouse might be fine with Logitech but I don't like it.

If this is about votes, maybe other MM users can check out, and vote for, this bug.

Repro Steps:
1. Create two identical blocks of text
2. In first block of text insert a new paragraph (Hard Return) - press [Enter]
3. Select all the text of the first block and add paragraph spacing (I used 40 to exaggerate)
4. Note the space between the two paragraphs increases to 40 px(?) {expected}
5. Second bock of text at the same point add a soft return - press [Shift + Enter]
6. Select the all the text in the second block and add a paragraph spacing of 40.
7. Note that the point where the soft return was entered no space should be added. The space at the end of the paragraph should extend.
8. Click out side of the second block (the Soft Return block of text)
9. The space where the Soft Return was entered jumps and is now showing similar to the Hard Return block of text.

Expectation:
The paragraph spacing should not be applied to a Soft Return.

Requirement text:
As a user I shall not see paragraph spacing applied where a Soft Return is used at all times.

Adobe XD version: 19.2.22.3 (Starter)

There is an issue with paragraphs when opening PSD into XD.
If you create a paragraph with a certain height and set baseline shift property it shifts out of place when opened with XD.

As for now, there are two ways:
1) use photoshop to convert text fields to point text
2) use xd to convert all text fields to point text and adjust the position

Problem: Both of these ways are too slow.

We have many artboards and they are layer heavy we had to separate them in multiple PSDs because they are starting to get unusably slow.

Someone already posted this issue and it's marked as solved but for me, that's not the case:
https://adobexd.uservoice.com/forums/353010-adobe-xd-bugs/suggestions/33756346-issue-with-photoshop-to-xd-type-fields

As a user, I want to be able to adjust the auto save frequency on cloud documents so that I have more control over my system and my file, and my workflow is not interrupted.

Right now, the auto save seems to save my work every X edits, which would be great if XD didn't slow down or freeze during this, unfocus typing, and generally interrupt my entire workflow.

For example this just happened to me again: I manually saved a document. Then I clicked into an element (not component) and adjusted the text, then I clicked on the parent element and used alt+drag it to create a copy. While dragging, the auto save feature kicked in, which unfocused my alt+drag, leaving the parent element moved instead moving a duplicate element. Pressed ctrl+z, then used alt+drag on the parent element again, only to have auto save invoked again only this time after I regained control, XD registered the alt+drag on a different element, creating a copy of that one.

Imagine this and similar situations literally 10-12 times an hour. Because you can only use cloud documents to create design systems and you can't replace a cloud document with a different local version, this undesirable execution of a feature makes using design systems difficult.

Please consider allowing us to adjust the frequency of auto save for cloud documents, or at the least allow us to turn off auto save.

Thank you for your time!