Anki 2.1.55 Beta 1-2

It can already take up half the window, so long as you’ve got enough tags. The max-height of the pane increases with each new line.

There’s no point in having a tag editor that is bigger than the stotal space taken by the tags of the current note. When you add new tags, the pane should automatically grow when you reach a new line.

Linux Qt6

Adding a new tag (pressing enter when one is selected) sometimes adds an empty tag

I have not been able to figure out how to reproduce it reliably, but it happens quite often for me (sometimes a new tag appears and is then deleted)


My suggestion for menu design (inspired by Windows 11):

                      background-color: hsla(0,0%,98%,.9);
                      border: solid 2px rgba(0, 0, 0, 1);
                      border-radius: 8px;
                       box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);
                QMenu::item {
                        background-color: transparent;
                        padding:3px 15px;
                        margin:5px 10px;
                        color: rgb(26, 26, 26);
                        font-weight: 460;
                QMenu::item:selected {
                        background-color: rgb(195, 195, 195);
                        border-radius: 4px;

and a raised menu bar (better for touch screen users):

QMenuBar {
    background-color: #F3F3F3;


QMenuBar::item {
                        background-color: transparent;
                        color: rgb(26, 26, 26);
                        font-weight: 460;

QMenuBar::item:selected {
                        background-color: #EAEAEA;
                        border-radius: 4px;

QMenuBar::item:pressed {
    background: #888888;
1 Like

Some notes:

It would be better if the symbol of the pin above the field in the edit appears all the time. For a moment I asked myself where he had gone.

It is better to distinguish more between a radio button and a button with a V marking. And also to add a border to them in dark mode because it’s a bit hard to see them.

It also bothered me that the buttons that raise or lower a number in spinbox are hidden until hovering. It looks as if it is waiting to be typed. It is also less convenient to have to “travel” with the mouse from side to side of the box to raise or lower a number.

And a small bug, in deck settings, if the description appears above and not below, sometimes the letters are blurred.

I used automatic translation because it is difficult for me to write in English (maybe Anki will help with that?!) If something is not clear I will try to explain more.

Have to disagree. At least for desktop it should not be a usability issue and drastically improves readability of field states. But of course the majority has to decide.

For mobile one could argue that hover is not possible, so we could show the badges there.

Because it is. These inputs are primarily text (number) inputs and the arrows are for convenience when you want to fine-tune a value.

I’ll revert the horizontal design to a vertical one, if that’s what people prefer.


I’m not sure if this is a new problem, but it looks like the field name in the Add dialog overlaps the contents of the field when you scroll down.

I have been seeing this same behavior on Windows Qt6. It happens consistently for me if I type the portion of the text of an existing tag, select it with my keyboard, and then hit ENTER.

If I use a new tag name, then an empty tag does not appear. If I type the entire name of an existing tag (not using autocomplete), then the empty tag appears and immediately disappears.

The empty tag appears after the blinking cursor (where I would type another tag).

Another problem

In the Card Browser, when a card is first selected, the top row of buttons, including “fx” initially appear gray (indicating they are disabled).

Clicking anywhere in the card edit panel causes the buttons to become ungrayed. However, clicking one of the buttons while it is grayed out triggers the button’s effect, so it’s not actually disabled it only appears to be. In the case of the fx button, clicking it while it is grayed causes the menu to flash open and immediately close.

There have definitely been some performance regressions, but that is still surprisingly slow - on my machine it takes about 2-3 seconds to perform that action. Assuming it’s not an ancient machine, maybe your antivirus is slowing things down?

The plan is to drop that option in the future, so we didn’t want to waste translator’s time.

I can’t seem to reproduce this - does it still happen for you?

Thanks, should be fixed.

Maybe that would make more sense. Currently it’s configured via the Fields dialog.

Easiest: have the users export with the legacy compatibility option enabled in the export screen.

1 Like

Great job! It was about time to give Anki the UI it deserves. :slightly_smiling_face:
Here is some stuff that caught my eye:

  1. grafik
    Are these labels centered? Maybe the box is too small? The ‘p’ doesn’t look right so close to the border.

  2. grafik
    I would make the knob smaller or the path larger, like the toggles in deck options. Curved hair lines can’t be rendered evenly.

  3. grafik
    As @cqg said, these lines are almost invisible. But also, there shouldn’t be a border below the active tab. Strange that it looks different for you, even though we’re both on Win 10.

  4. grafik
    That’s how tooltips look in night mode.

  5. grafik grafik

    I like how the horizontal split uses browser space more efficiently, but there are some issues:
    i) Column headers behave weirdly when scaling columns (screenshot 1).
    ii) If there are rows, an extra column appears on the left (screenshot 2). This is not new, but now this column is significantly wider. I think it’s only purpose is to allow selecting everything or an entire row, which is not very helpful in Anki’s case. Maybe it can be removed completely.
    iii) On older releases, the editor appears now on the side as well. Bug or feature?

1 Like

If you want to support the new format as well, you need zstd to decompress.

1 Like

Somewhat related discussion: Default Editor settings instead of persistent

The current behavior is weird, agreed. Switching to a note of the same notetype should keep the current state. But switching to a different notetype, the field probably has a completely different job, so it should reset to a default (or the setting of the last note of that notetype).

Maybe we could remove the setting from the fields dialog. But I don’t know how feasible a per-notetype entry in the profile manager would be.

1 Like

On a fresh install, Anki 2.1.55 says that the parameters are not in the default configuration.

1 Like

I reinstalled Anki and I cannot reproduce now.

I am using a 4 years old Acer Swift SF113-31. It does show some signs of age, but all in all it is a quite average machine I guess?
I also tried disabling my antivirus and did not see much improvement.

In the Add window, if the tags panel is open when the window is resized to have a smaller height, then the tag panel shrinks such that the tags are no longer visible.

I think adding the shrink image feature is an incredible idea. I’ve been using the Shrink Image Size In Editor (1633333766) and I love being able to do this.

I like the button that toggles the images in the browser.
I think by adding an option to click and expand a single image (with the default being whatever is toggled) would be immensely helpful.
If that isn’t possible is there a shortcut for toggling the shrink button?


Thank you so much for adding such a useful feature to anki.

I’m a bit confused by your question - doesn’t double-clicking a small image to expand it do what you want?

No it shows up as an option but when the images are shrunk when double clicked nothing happens. Same in reverse. The gear is the only way to change it. I’ve loaded anki with no add ons and the problem still persists.

Hi, I’ve noticed that --focus-border and --focus-shadow aren’t used anymore. Please use a variable for the focus color.

Edit: Sorry, it is indeed using the very same variable. But the variable has been changed to --border-focus. Please consider to change this back to how it was.

Those have been renamed to --border-focus and --shadow-focus. Reason being the new Sass map structure / naming scheme, where the thing a color is used for (e.g. border, shadow, canvas, accent etc.) is the parent for multiple variations (e.g. -subtle, -disabled, -faint etc.).

1 Like