Currently, when applying a TranslateZoomRotateBehavior to an Element, two 'Friction' Properties are offered, one for Rotation and one for Translation.

However, when inputting custom numerical values, in Studio, they automatically 'snap' back to a value of '1', whilst in the XAML for the file, they correctly reflect the manually-input value.

(Furthermore, I'm not entirely convinced that these Property Values produce any effects on the Page when in Play Mode - I could however be wrong)

See attached video.

Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml

2) Select the root Grid, and change its dimensions to 800x800

3) Introduce a Rectangle Element to the Page, placed within the rootGrid, and set its dimensions to 256x256.

4) Navigate to the Interactivity Panel, and with the Rectangle selected, apply a TranslateZoomRotateBehavior Behavior to it.

5) With the Behavior selected, identify its 'Translate Friction' and 'Rotational Friction' Properties, and manually adjust each of them to feature a custom value.

Observe how the value 'snaps' to '1'.

6) Save MainPage.xaml, then open it in VSCode, and identify the 'Translate Friction' and 'Rotational Friction' Properties.
Observe how in the XAML, they are correctly displaying the values selected in Step 5).

7) As a bonus step, attempt to adjust the 'Translate Friction' and 'Rotational Friction' Property values to produce any noticeable effect on-Stage in Play Mode. I personally wasn't able to produce any results in either, but it could be due to a misunderstanding on the functionality they provide.

Expected Results: Values input into the 'Translate Friction' and 'Rotational Friction' Properties correspond to the values input in the Behavior's Properties Panel.