Let's flush whatever was in the input box.

[Aleksandar Kovač]

On the second keystroke, some input boxes in V2 apps flush whatever value there was and accept values from that 2nd keystroke on...

Try?

1. Create a new file but do not select 'Create artboard' option.
2. Go: context bar 'Document setup...', 'Dimensions' tab.
3. Position cursor in front or in between digits in either X or Y document dimension input box.
4. Type two digits -> BUG: on second digit, input box empties and the value is replaced by your second digit only.

Why is this problematic?

• Unnecessary and unintuitive disruption of the workflow.
• No observable benefit of the current behavior.
• (Most likely, temporal) loss of user settings.
• Annoyance by the fact that one of the oldest known GUI elements in window metaphor UI paradigm has not been implemented properly.

You can play with it. Select a digit then type, select the whole value and type, and so on... This bug has been appearing throughout V2 applications. Some instances are repeatable, some not, which only adds to workflow disruption.

Probably related to...

 

[MikeTO]

Hi Aleksandar, unfortunately this is a known issue. Hopefully it's fixed in an update in the near future.

[NathanC]

Hi @Aleksandar Kovač,

I've now bumped the logged issue with your report.

[NotMyFault]

Don’t now if related or not, but symptoms look kind of similar:

Occasionally Safari on MacOS (Apple keyboard/BT) and / or iPad (with physical Logitech keyboard only) accepts the first letter, but them jumps back to the first position of line, and enters all following characters there before the first character. So the first letter gets shifted to the right with every letter.

As I can’t accidentally hit the enter key (unnoticed) which is far away on the right side of keyboard, i assume this may be a general Apple issue with some keyboard.

[Affinity Info Bot]

The issue "[macOS Monterey, Big Sur] Resize Canvas, Resize Document, Transform panel input fields: issues when entering values" (REF: AFP-5856) has been fixed by the developers in internal build "2.1.0.1720".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.