I believe the point highlighted is about the pinning of text frame inside the button frame, which when stretched was dragging the text frame in previous versions. If we see this closely we would find that the text frame inside button was page pinned so it should maintain its pinning distance with page center (center pinning) , but it was eventually not maintaining the center distance in previous releases and was increasing on stretching the button frame. So the page pinning was actually not working on text frame inside button in previous release, which now works in current release. In this release page pinning does behaves like a page pin and maintains the distance as per the page element is pinned. - Center Page pinning should maintain the distance from page center - Right page pinning should maintain the distance from page right edge - Left page pinning should maintain the distance from left page edge Another change is that Nested elements are no more allowed for pinning when they are responsive, as when page element is set to responsive and is nested within any parent container then by default the fluid pinning will act and page element would maintain the distance from parent container frame. For example, when a rectangle is inserted in composition target and composition is set to responsive resize : - Scrubbing through breakpoints resizes the target as well the rectangle inside target. When rectangle is set to resize none inside target and page pinned : - Rectangle will be pinned in respect to its parent container which is the target, so pinning will maintain the distance between the rectangle edge and target edge. - Composition target on scrubbing will resize till the point when rectangle frame edge touches target frame edge, the parent container(target) will respect the resize and pinning behavior set to rectangle. When target is also set to pin on page : - On scrubbing the target will maintain its position on page as per page pinning applied to it. - Child element(rectangle) will maintain the pinning with respect to target edge. The change with pinning behavior was enrolled due to complexity of scenarios with child-parent element when pinned. As now we have all widgets supporting responsive behavior , we have tried to rectify the workflows which were not working accurately before. Thanks, Sanjit
... View more