When calculating REM via trem, the active cursor sometimes isn’t set properly.
Workflow wise, I don’t think it’s an issue at all since I wouldn’t want to edit the calculated value anyway.
Tested with Firefox and Edge.
When calculating REM via trem, the active cursor sometimes isn’t set properly.
Workflow wise, I don’t think it’s an issue at all since I wouldn’t want to edit the calculated value anyway.
Tested with Firefox and Edge.
Hi @Marius,
Thank you for taking the time to report this!
I have been able to reproduce this issue on my end.
It appears that the cursor misalignment occurs specifically when there are four digits after the decimal point (0.xxxx).
We’ll be sure to find a fix for this.
Apologies for the inconvenience.
@Araminta different issue, but related to “trem” shortcut.
It seems it doesn’t work on the global H’s.