Adrian

Anything missing here from your side, since this PR is still marked as Draft?

There's a small regression: When you registered and view your registration, the dropdown to change your consent for the participant list is now much harder to see. I already fixed...

I recommend adding some wrappers for the different object types - check the `PersonLinkListFieldBase` subclasses in Python what roles we set and on which conditions this depends.

yeah... unless we want to move all dialogs in one go, which might actually not be such a bad idea considering the huge amount of awful complexity the wtforms-based backend...

> I added 2 test fields on RegistrationPrivacyForm for visual testing. Could you split that into a separate commit please? That way it's easier for us to just remove that...

In the end I think this is not particularly useful, also because it's very easy to get the checks wrong - for example, right now it would almost certainly fail...

FWIW this is the error I get when sending `{"field_825794":{"lol":69}}` as the payload to update a registration: ```pytb File "/home/adrian/dev/indico/py3/src/indico/modules/events/registration/util.py", line 487, in modify_registration new_data = snapshot_registration_data(registration) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/adrian/dev/indico/py3/src/indico/modules/events/registration/util.py",...

I just tested with `babel==2.15.0` which uses CLDR 44, but on de_DE I still get `Mo., 9. Juli` when using `format_skeleton('EEEEdMMMM')`. I also tried using the native Babel `format_skeleton` instead...

Can't we make the skeleton format string translatable and thus use a nice one for languages that support it, and another one for other languages?

True, it's more something we would want to manage and not leaving it up to translators. How easy is it to check if a particular skeleton exists and falling back...