<feed xmlns='http://www.w3.org/2005/Atom'>
<title>searxng/.git/searx/templates/simple/page_with_header.html, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.slickd.xyz/searxng/.git/'/>
<entry>
<title>[mod] template preferences: split into elements (no functional change)</title>
<updated>2023-06-02T17:05:43+00:00</updated>
<author>
<name>Markus Heiser</name>
<email>markus.heiser@darmarit.de</email>
</author>
<published>2023-06-02T13:30:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.slickd.xyz/searxng/.git/commit/?id=2149e88bdd64a66d867ad1f5c46e6aa0977d837a'/>
<id>2149e88bdd64a66d867ad1f5c46e6aa0977d837a</id>
<content type='text'>
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 &lt;markus.heiser@darmarit.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &lt;markus.heiser@darmarit.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>[simple] introduce page_with_header.html template</title>
<updated>2022-01-30T16:29:21+00:00</updated>
<author>
<name>Martin Fischer</name>
<email>martin@push-f.com</email>
</author>
<published>2022-01-30T08:39:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.slickd.xyz/searxng/.git/commit/?id=6f0ec7e58f9c7c9d188561296546ec139e1f9118'/>
<id>6f0ec7e58f9c7c9d188561296546ec139e1f9118</id>
<content type='text'>
Previously the preferences &amp; stats templates contained the markup:

&lt;a href="{{ url_for('index') }}"&gt;&lt;h1&gt;&lt;span&gt;SearXNG&lt;/span&gt;&lt;/h1&gt;&lt;/a&gt;

There are many things wrong with this:

1. the markup was duplicated

2. the CSS needed to be changed whenever a new page wanted to use this
   header (since the CSS used page-specific selectors)

3. h1 should be reserved for the actual page title
   (e.g. Preferences or Engine stats)

4. the image was set via CSS which also set:

       span { visibility: hidden; }

   which however removes the alternative text from the accessibility
   tree (meaning screen readers will ignore it).

This commit fixes all these problems.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously the preferences &amp; stats templates contained the markup:

&lt;a href="{{ url_for('index') }}"&gt;&lt;h1&gt;&lt;span&gt;SearXNG&lt;/span&gt;&lt;/h1&gt;&lt;/a&gt;

There are many things wrong with this:

1. the markup was duplicated

2. the CSS needed to be changed whenever a new page wanted to use this
   header (since the CSS used page-specific selectors)

3. h1 should be reserved for the actual page title
   (e.g. Preferences or Engine stats)

4. the image was set via CSS which also set:

       span { visibility: hidden; }

   which however removes the alternative text from the accessibility
   tree (meaning screen readers will ignore it).

This commit fixes all these problems.
</pre>
</div>
</content>
</entry>
</feed>
