You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Dropbox Sign: Rotating signature boxes
Uploading a PDF with both landscape and portrait images, and using Dropbox Sign….When I am configuring "Signature Boxes", “Date/Initial" boxes etc in Dropbox Sign, it seems that i cannot rotate the s...
Hey all, I'm the engineering lead for the involved team.
I'm really sorry about the frustration this has caused. It really is a bit of a tricky problem for us to solve on or end — PDFs are hard! — but we have been working on it, and I understand how critical a timely fix would have been for many of you.
My team was able to reproduce the issues noted in this thread by a few PDFs provided to us by our Support team that displayed the errant behavior. We used these to help validate our work and now, using these files, we see fields oriented as expected.
A couple of weeks ago, we released a patch which should reconcile the conflict between field rotation and PDF orientation.
Fields should now be oriented relative to the top of the file viewer, and not based on the underlying PDF encoding. If you rotate a document in the viewer, any fields you've added will be cleared so that field orientation will be correct to the new orientation. You'll get a warning before this happens, so you can go cancel the action if you need to.
If you are still seeing fields oriented the wrong way, could you please share a sample PDF with our Support team (dropbox.com/support) so that we can take another look and make sure we didn't miss an edge case? Just make sure the file doesn't contain any private or sensitive information.
Rest assured, my team does really care, but like with many companies we have a number of other priorities we need to juggle as well, and we're all doing our best.
Hannah
Dropbox Staff
Dropbox StaffHey Jonathanrm1, sorry to see you're having this issue.
This is an issue that our team is actually aware of and currently working on a solution.
I moved your post to the relevant thread, so you'll get an email when there's an update from the team.
I hope this helps.
Can we get an update on progress, the 'team' have been looking into this for weeks. Something that should be a relatively simple fix, considering it worked correctly previously. Some needs their head wobbled
