Custom Fields are semi broken since today

[mirai-ux]

Since the latest commit asbplayer custom fields seem to have been broken. My entire config got erased, and due to my own stupidity my backup was old enough that I had to change some of the custom fields. Well, for some reason now they automatically get sorted in an alphabetical order, so I could create fields: Target Word 1; Reading 1; Definition 1, all in this particular order, only for Reading to immediatly jump ahead of Target Word, and Definition ahead of them both.

[killergerbah]

Do you mind uploading a video of the problem? I can't seem to reproduce it and it would be helpful to know the exact steps you're taking.

[mirai-ux]

2024-04-22.09-02-44.mp4

Every time i turn on the browser (using vivaldi because ff codec support is not great TM) the fields just get sorted alphabetically. I have to import my json file for it to work normally. Closing and reopening the app breaks it all over again. That and sometimes it just randomly does it in the middle of the session too.
I haven't installed any new extensions since setting everything up, nor have I played around with the browser's settings. Maybe a new Vivaldi update bricked something?

[killergerbah]

I would guess that it was a Vivaldi update (although even if that is the case, this is pretty baffling behavior). I did release some code a couple days ago, but no changes were made to the settings UI, at least none that would cause an issue like this. I'll still take a look to verify these claims and see if there are any workarounds.

[killergerbah]

Okay, I believe I know why this issue might be happening. The custom Anki fields settings don't have any ordering data and so the order in which they appear in the settings UI or Anki dialog is entirely dependent on how the browser decides to sort the dictionary when retrieving it from storage. So this is not entirely a problem with the browser (it happens on Chrome too if you refresh the page) since the data model itself is flawed and doesn't preserve ordering. The only thing that confuses me is why it hasn't appeared until now.

I think a fix for this might be somewhat complicated and a little risky since I will need to migrate settings data to a new data model. So you may have to live with this for some time. The workaround I would suggest is to put numbers in front of the field names for your custom fields.