searxng/.git/searx/templates/simple/preferences/infinite_scroll.html, branch master Unnamed repository; edit this file 'description' to name the repository. [mod] client/simple: client plugins (#5406) 2025-12-02T10:18:00+00:00 Ivan Gabaldon igabaldon@inetol.net 2025-12-02T10:18:00+00:00 fb089ae297b27f51777318e3a28bca8b172a4165 * [mod] client/simple: client plugins Defines a new interface for client side *"plugins"* that coexist with server side plugin system. Each plugin (e.g., `InfiniteScroll`) extends the base `ts Plugin`. Client side plugins are independent and lazy‑loaded via `router.ts` when their `load()` conditions are met. On each navigation request, all applicable plugins are instanced. Since these are client side plugins, we can only invoke them once DOM is fully loaded. E.g. `Calculator` will not render a new `answer` block until fully loaded and executed. For some plugins, we might want to handle its availability in `settings.yml` and toggle in UI, like we do for server side plugins. In that case, we extend `py Plugin` instancing only the information and then checking client side if [`settings.plugins`](https://github.com/inetol/searxng/blob/1ad832b1dc33f3f388da361ff2459b05dc86a164/client/simple/src/js/toolkit.ts#L134) array has the plugin id. * [mod] client/simple: rebuild static 
* [mod] client/simple: client plugins

Defines a new interface for client side *"plugins"* that coexist with server
side plugin system. Each plugin (e.g., `InfiniteScroll`) extends the base
`ts Plugin`. Client side plugins are independent and lazy‑loaded via `router.ts`
when their `load()` conditions are met. On each navigation request, all
applicable plugins are instanced.

Since these are client side plugins, we can only invoke them once DOM is fully
loaded. E.g. `Calculator` will not render a new `answer` block until fully
loaded and executed.

For some plugins, we might want to handle its availability in `settings.yml`
and toggle in UI, like we do for server side plugins. In that case, we extend
`py Plugin` instancing only the information and then checking client side if
[`settings.plugins`](https://github.com/inetol/searxng/blob/1ad832b1dc33f3f388da361ff2459b05dc86a164/client/simple/src/js/toolkit.ts#L134)
array has the plugin id.

* [mod] client/simple: rebuild static
 [chore] docs: various grammatical fixes 2025-06-23T21:01:29+00:00 benpiano800 51756721+benpiano800@users.noreply.github.com 2025-06-12T15:24:43+00:00 b47ee0a4e338f86761cb871496852b71594fceb0 






[fix] simple template: add ID to elements used for aria-labelledby
2024-09-21T13:23:21+00:00

Markus
markus@venom.fritz.box

2024-09-15T15:08:57+00:00

8b8d830fd367386c5f06ae5a427028dc12642cd1

The ``aria-labelledby`` [1] attribute identifies the element that labels the
element it is applied to.  The templates ``infinite_scroll.html`` and
``search_on_category_select.html`` define a ``aria-labelledby`` at the <input>
tag but miss the id in the <div> with the description.

[1] https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-labelledby

Signed-off-by: Markus <markus@venom.fritz.box>





The ``aria-labelledby`` [1] attribute identifies the element that labels the
element it is applied to.  The templates ``infinite_scroll.html`` and
``search_on_category_select.html`` define a ``aria-labelledby`` at the <input>
tag but miss the id in the <div> with the description.

[1] https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-labelledby

Signed-off-by: Markus <markus@venom.fritz.box>







[fix] Removes ``/>`` ending tags for void HTML elements
2024-09-21T13:23:21+00:00

Markus
markus@venom.fritz.box

2024-09-15T15:05:02+00:00

67fcf3cc67c842aebd512922a751d0ebe1bb9264

continuation of commit: 0b832f19b

Signed-off-by: Markus <markus@venom.fritz.box>





continuation of commit: 0b832f19b

Signed-off-by: Markus <markus@venom.fritz.box>







[feat] settings: replace boolean select preferences with checkboxes
2023-08-27T19:23:43+00:00

Bnyro
bnyro@tutanota.com

2023-08-20T12:03:03+00:00

e5535ec078776d07d8eeac0d51dc8f17f77cfb27












[mod] template preferences: split into elements (no functional change)
2023-06-02T17:05:43+00:00

Markus Heiser
markus.heiser@darmarit.de

2023-06-02T13:30:02+00:00

2149e88bdd64a66d867ad1f5c46e6aa0977d837a

HINT: this patch has no functional change / it is the preparation for following
      changes and bugfixes

Over the years, the preferences template became an unmanageable beast.  To make
the source code more readable the monolith is splitted into elements.  The
splitting into elements also has the advantage that a new template can make use
of them.

The reversed checkbox is a quirk that is only used in the prefereces and must be
eliminated in the long term.  For this the macro 'checkbox_onoff_reversed' was
added to the preferences.html template.  The 'checkbox' macro is also a quirk of
the preferences.html we don't want to use in other templates (it is an
input-checkbox in a HTML form that was misused for status display).

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>





HINT: this patch has no functional change / it is the preparation for following
      changes and bugfixes

Over the years, the preferences template became an unmanageable beast.  To make
the source code more readable the monolith is splitted into elements.  The
splitting into elements also has the advantage that a new template can make use
of them.

The reversed checkbox is a quirk that is only used in the prefereces and must be
eliminated in the long term.  For this the macro 'checkbox_onoff_reversed' was
added to the preferences.html template.  The 'checkbox' macro is also a quirk of
the preferences.html we don't want to use in other templates (it is an
input-checkbox in a HTML form that was misused for status display).

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>