Hey @JorikSchellekens, on:

1. Use only one of the input methods
2. Use both methods but have only one available at a time according to a toggle
3. Use both methods which mutually update each other as displayed in the screenshots

Let's stick to the designs, as per (2), where:

• The stepper isn't labelled with numbers
• There's a toggle to enable custom input
• When custom input is enabled, the stepper enters a disabled state

• Test if first clicks on the slider are more performant without animations
• R&D letting browsers know text sizes could change in advance to avoid poor performance on first clicks (worth pairing on with Bruno)
• Nad & Rok to look again at interactions between slider & custom— switching between the 2 feels strange, clicking on the slider steps is hard, font size values are abstract (consider using 100% as default and letting users input relative to that), solve slider not scaling
• Nad to get better clarity on values (up to 20px is safe)
• Nad to dogfood + make a list of obviously broken stuff

Thanks @turt2live for the lints. They should all be cleaned up now. Wondering if we can add lowercase css variables to the linter

@JorikSchellekens this has conflicts and doesn't look like the last review was actually resolved? (no pushed commits)

Woops sorry @turt2live , pushed them now

Definitely seems like a smoother experience without the animations. The screen jump as a result of font size change isn't overly disturbing

I'm not getting poor performance, and without the animations I think it's no longer a problem.

We decided to have the slider reactivate itself if it was disabled and it was clicked on. However, with the way the settingtoggle currently works that's a little awkward to do. I'll have a look at clean way of doing this when experimenting with checkboxes under the new appearance tab.