| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "search.html" template will generate a warning admonition about
requiring JavaScript for search and automatically hiding the element
when supported. While functional, if a client renders the page slowly,
the warning notification may be visible to the user for a moment.
Instead of relying on JavaScript to suppress this warning, use a
`noscript` tag to hide the warning for clients who do not support
JavaScript. This also has the benefit of one less JavaScript call
required by a client.
Signed-off-by: James Knight <james.d.knight@live.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In particular mobile browsers use correction mechanisms on input fields.
Search will often be done with technical terms or even class/method/etc
names that these correction mechanisms do not know, resulting in unwanted
changes. This PR deactivates these correction mechanisms.
While I haven't been able to find official reference documentation on
these input attributes, there are multiple sources, describing this, e.g.
References:
- Autocomplete: https://www.w3schools.com/howto/howto_html_autocomplete_off.asp
- Spellckeck: https://www.w3schools.com/howto/howto_html_spellcheck_disable.asp
I did not find official reference docs on autocorrect and autocapitalize, but
they are mentioned in various sources, e.g.
- https://mgearon.com/html/disable-autocomplete-autocapitalize-and-autocorrect/
- https://stackoverflow.com/questions/35513968/disable-auto-correct-in-safari-text-input
- https://davidwalsh.name/disable-autocorrect
and it works, as can easily be checked with a mobile device on the demos in the above
links.
|
| |
|
| |
This allows themes to customize the default search page.
|
| |
|
|
|
|
|
| |
.. note::
$ find sphinx tests LICENSE doc/conf.py -type f -exec sed -i '' -e 's/2007\-20../2007-2021/' {} \;
$ git co sphinx/locale/**/*.js sphinx/templates/epub3/mimetype
|
| |
|
|
|
| |
The ``language_data.js`` is only used on search page. But it is always
loaded meaninglessly. This fixes not to load it on all non-search pages.
|
| |\ |
|
| | | |
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In HTML5, <script> elements default to MIME type text/javascript. The
HTML5 living standard and MDN recommend against including the attribute.
From https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script#attr-type
> The HTML5 specification urges authors to omit the attribute rather
> than provide a redundant MIME type.
From https://html.spec.whatwg.org/#the-script-element
> Authors should omit the type attribute instead of redundantly setting
> it.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This change removes odd-looking empty lines before the doctype declaration in
HTML files created by jinja templates.
|
| | |
|
| | |
|
| |
|
|
| |
asynchronously.
|
| | |
|
| | |
|
| |
|
