You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed when using the list-search macro, the filter option is different from the text input.
You define the filter in the macro-call, for instance "[tag[Definitions]]" (or use default filter "[tags[]]").
Then, the text you write into the text input narrow down the search to the filtered titles matching the text input.
For instance (on Tiddlywiki.com) with the filter option "[tag[Definitions]]" and the text "URI", you would only see two elements in the list: Data URI and URI.
In your use-case, the text input is replacing the filter option.
On the GG Eskha proposed:
Indeed when using the list-search macro, the filter option is different from the text input.
You define the filter in the macro-call, for instance "[tag[Definitions]]" (or use default filter "[tags[]]").
Then, the text you write into the text input narrow down the search to the filtered titles matching the text input.
For instance (on Tiddlywiki.com) with the filter option "[tag[Definitions]]" and the text "URI", you would only see two elements in the list: Data URI and URI.
In your use-case, the text input is replacing the filter option.
For other, I add a link to your well explained "demo/list-search-macro" tiddler:
Shiraz 2.1.2 — extended markups: styles, macros, images, tables (kookma.github.io)
To summarize, what would be my "ideal" behavior would be that an optional "entries-per-page" attribute exists in list-search!
The text was updated successfully, but these errors were encountered: