MaskedAvenger said:
Is there a rationale for this? Especially the navbar option. I also use a "phrase completer" program to enter tags, so I do find tag autocomplete somewhat redundant for several tags.
Navbar rationale:
Remove the enable_sequential_post_navigation option. This option was used to disable the next/previous post navbar below posts.
This option was originally added in issue #674 because of people complaining about the navbar when it was originally added. Also there were complaints about URLs being uglier because of search params in the URL (e.g. /posts/1234?q=touhou). There were also various minor bugs with it at the time, such as keyboard shortcuts not working correctly, or the
page not remembering your search after a tag edit.
These complaints are irrelevant nowadays because a) people are used to the navbar by now (and more often complain about it *not* being there for order:score searches), b) post URLs always contain the search now, this option hasn't disabled that for years, and c) the initial bugs with it were fixed years ago.
Source: https://github.com/danbooru/danbooru/commit/b6fef7f3f3967188a7c68b7b826f97199e815699
However, just use custom CSS to hide the navbar if you don't like it.
#c-posts #a-show #nav-links {
display: none;
}Autocomplete rationale:
This option was originally added in issue #1747. But only ~350 users ever disabled autocomplete, only ~120 of these were seen in the last year, and only 9 new users who signed up in the last year disabled it.
Users wishing to disable autocomplete can use this CSS:
.ui-autocomplete { display: none !important: }or this Javascript:
$("[data-autocomplete]").autocomplete("disable");Source: https://github.com/danbooru/danbooru/commit/d408ccbd418c6fbe530faf288b3f6700df9e44c8
I'll note that using the CSS option won't keep your browser from querying the network to fetch the information for autocomplete.
