Closed hafu closed 2 months ago
Hi @hafu , thanks for reporting. The last commit should fix the bug. If you have time, you can install the wheel from the GitHub action once it is completed.
Thanks for the quick fix! I've tested it and it works.
Awesome, thanks! We will publish the new version later this week. Lets see what else comes up.
Description / Beschreibung
When using a option set provider with autocomplete widget, which uses
refresh = True
inside a collection on page level (is collection), the user can not switch between the tabs / sets and is stuck at the last created one, if a new one is created or the first one when answering the questions.This only occurs on option set providers inside a collection with
refresh = True
. For example with rdmo-plugins-gnd.Expected behaviour / Erwartetes Verhalten
The user can switch between tabs / sets.
Steps to reproduce / Schritte zum Reproduzieren
refresh = True
on a page which is a collectionPage with is collection enabled and a question using an option set provider with
refresh = True
as autocomplete widget type: The user can not switch to "test1" after creating "test2" and is stuck on the last created one.Or if already filled out:
Page with is collection enabled and a question using an option set provider with
refresh = True
as autocomplete widget type: After the user browsed to the page, the user can not switch from "test1" to "test2".Note: In the example screenshots the rdmo-plugins-wikidata plugin was used, which does not use
refresh = True
by default. It was modified for testing purposes by setting therefresh
flag toTrue
. A better example is the rdmo-plugins-gnd plugin.Context / Kontext
References / Verweise
*