Tagging conditional parking restrictions seems very uncomfortable/error-prone

[SupaplexOSM]

Parking restrictions (e.g. "no_parking", "loading_only") can be conveniently selected via a drop-down menu. That's perfect.

However, there is no direct way to map a conditional restriction. To do this, it is necessary to specify a "restriction" first, to make the "restriction:conditional" field appear. The editor assumes that a non-conditional "default" restriction has to be present to add a conditional restriction. This is inconvenient, as this is not the case normally. (For "fee", this might work, but for "restriction" or "maxstay", that seems unfavourable.)

Maybee it's better to make the conditional fields always visible or add a check box "[ ] conditional" that expands a conditional input field? In case of "restriction", it would be also nice to have a drop down menu for the first part of the conditional restriction, as there are only a few limited options and so that one does not have to enter "loading_only" etc. manually.