[BUG]: Unnecessary "next" card option in CardTemplatePreviewer
Checked for duplicates?
- [X] This issue is not a duplicate
What are the steps to reproduce this bug?
- Open a note created using the
Basic (optional reversed card)notetype in the Note Editor. The note should not have a reversed card. - Open the preview of the card.
Expected behaviour
The forward card is seen in the preview and there are no > (next) or < (previous) options associated with the Show/Hide answer button.
(Screenshot from the preview of a card created using the Basic notetype)
Actual behaviour
The Show/Hide answer button shows > (next) or < (previous) options.
On clicking the > button, it shows:
On the Desktop version, clicking the next button shows the next card (from the next note). It makes sense because the note editor and the browser are inseparable there.
However, in AnkiDroid, I think that it makes more sense to hide the button when there is no reverse card associated with the note.
Debug info
2.17 alpha 14
(Optional) Anything else you want to share?
No response
Research
- [X] I am reporting a bug specific to AnkiDroid (Android app)
- [X] I have checked the manual and the FAQ and could not find a solution to my issue
- [X] (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)
When the note actually has a reverse card and the user is previewing the reverse card (by first selecting the reverse card in the browser), then clicking the next button doesn't do anything.
In this case, either
- the next button should be disabled and the previous button be enabled instead; or
- clicking the next button should display the forward card.
I am working on it!!
I thought about this for a while, and I believe that this can't be applied to the general scenario. There are people that will want to explicitly see that a card couldn't be generated, specially when there are many templates in the same notetype.
There are people that will want to explicitly see that a card couldn't be generated
This makes sense. But, my second observation is definitely unexpected and should be resolved.
#15554 solves that
In that case, I would be happy to get this issue closed when the new previewer is made the default one or there is atleast an option to enable the new previewer.