ankitects / ankitects/anki

Review/Preview screen does not always refresh when Special fields are updated

Open
#4,832 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
31.2k
Forks
3.2k
Avg merge
2d 8h
Merged PRs (30d)
72

Description

> Steps to reproduce
>
> Add {{CardFlag}}{{Tags}} to the basic note type’s template.
> Open the preview in the card browser.
> Make a new basic note.
> Flag the card (right click → flag → red). It still shows “flag0”.
>
> Alternatively:
>
> Click on “Cards…” and change the template. Then save and note that the preview hasn’t changed.
>
> If you mark the note (right click → notes → toggle mark) or more generally add/remove tags, it updates correctly.
> Expected behavior
> The preview should always update after flagging, changing the template or any event that can change the card.
> Debug info
> Anki 25.09.2 (3890e12c) (ao)
> Python 3.13.5 Qt 6.9.1 PyQt 6.9.1
> Platform: Windows-10-10.0.19045-SP0
>
> ===Add-ons (active)===
> (add-on provided name [Add-on folder, installed at, version, is config changed])
> Advanced Copy Fields ['1898445115', 2024-01-08T20:01, 'v0.4.01', '']
> AnkiConnect ['2055492159', 2025-11-09T22:40, 'None', mod]
> AnkiWebView Inspector ['31746032', 2023-06-27T22:26, 'None', '']
> Disconnected Review-Log Cleaner ['1067771610', 2025-06-10T16:28, 'None', '']
> Local Audio Server for Yomichan ['1045800357', 2023-06-19T06:57, 'None', '']
> The KING of Button Add-ons ['374005964', 2025-01-28T01:26, 'None', mod]
>
> ===IDs of active AnkiWeb add-ons===
> 1045800357 1067771610 1898445115 2055492159 31746032 374005964
>
> ===Add-ons (inactive)===
> (add-on provided name [Add-on folder, installed at, version, is config changed])
> No Distractions Full Screen Fixed by Shige ['1370336700', 2024-08-26T08:08, 'None', mod]
>

Originally reported on https://forums.ankiweb.net/t/bug-preview-does-not-update-when-changing-the-flag-or-template/69659

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the card browser with {{CardFlag}}{{Tags}} in a basic note template, then compare flagging and template changes with tag changes that refresh correctly. Trace the review/preview update entry point and the Cards… save flow. Done means the preview reflects flag, template, and other card-changing events without requiring an unrelated note or tag update.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
66/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.