Thank you for your post.
I am unable to replicate the issue using FileMaker Pro Advanced 15.0.2 under macOS Sierra 10.12.
I am not sure how your preset is 68%, as mine is 100%. Even after I change it to 68%, click OK, and come back to Page Setup, I can change it to 90%.
Let me know what other steps I need to take to replicate the issue.
Strange. My test file does it all the time, every time.
- New file
- 1 Table
- Add 1 Field:
- Interactive PDF
- Add new Record
- Insert PDF into Container (do not check "Store only a reference to file")
- Click on Container PDF to select it
- Choose "Page Setup…" from File menu
- Double click the "100%" in the "Scale" field
- Enter 90 or other valid number
- Press tab or return key
Temporarily create a new Mac user account, login to the new user account, launch FileMaker Pro Advanced 15.0.2 and repeat your steps above. Does the issue still occur?
There is a slight difference with the new Mac user:
When the page setup dialog opens, the scale (100%) is selected (highlighted) in the new Mac user. It was not selected in the original Mac user.
If I hit return while it is selected it works without error.
If I deselect the scale value by clicking behind the "%" and then reselect it before I change the the value (e.g. 100 to 90), it generates the same error message as the original Mac user.
Another difference that I found:
If I select the 100% (including the % character) instead of 100 which is what is selected when I double click the scale field, then it works correctly on the original Mac user too.
If I only select 100 and change it to 90, it generates the error message.
In other words, if I triple click the scale field (which selects all characters including the %), then it works correctly
I found some other 3rd party applications that have not been updated to macOS Sierra that behave the same way.
Thank you for the additional information. I can now replicate the issue.
Like you, I am able to replicate the issue in other applications (e.g., Safari, Chrome).
Although this is probably a macOS Sierra 10.12 issue, I have sent all information to our Development and Testing departments for review, so they can confirm and make sure Apple is aware of this issue.
I agree. It's most likely a macOS 10.12 issue.
Testing has replicated the issue, and confirmed it is a macOS Sierra 10.12 issue, as the error is reproducible in other applications.