Danbooru

DanbooruUp, tag completion for Firefox, Chrome, Opera

Posted under General

Speaking of feature requests, I'd like to have an option not to have any completion selected unless I choose one with arrows (and Tab to select the first candidate, the way Enter works currently, if possible). I find it very annoying that it frequently insists on completing a short tag I've typed manually to something much longer and completely incorrect.

Seconding Hazuki's request, although it might be nice to simply turn off auto-complete if what happens to be typed so far is a tag itself. I like the auto-complete feature, but it's rather annoying to have an actual tag auto-complete as the prefix of a slightly more frequent tag.

葉月 said:
Speaking of feature requests, I'd like to have an option not to have any completion selected unless I choose one with arrows (and Tab to select the first candidate, the way Enter works currently, if possible). I find it very annoying that it frequently insists on completing a short tag I've typed manually to something much longer and completely incorrect.

Wouldn't that make the feature slower to use? The way it works right now I typically type the first characters of each tag while fast pressing Enter and Space in between, and I'd rather not see more steps in this process.

Or as long as you can make this togglable whatever is fine then.

zatchii said:
I'll think about it. I usually just hit space if I don't want a tag completed.

The problem is I don't expect it to complete, and consequently don't remember to press space, when typing things such as hands which it then happily completes to hands_on_feet or similar. So when I then tap double Enter to commit it, it saves the wrong tag which I have to undo. Essentially, automatic completion is not the model I'm used to and it breaks the principle of least surprise. All the other completion systems I use, which are many, require an explicit action to trigger.

I think turning it off completely or forcing you to hit a key to trigger it would be somewhat annoying, which is why above I mentioned that perhaps the autocomplete should simply be suppressed when you type the entirety of an existing tag rather than autocompleting to a longer one. That way you don't have the problem Hazuki mentions nor do you have the inconvenience of not having autocomplete.

I've been noticing some issues with DanbooruUp too over the last few days, but it's not a FF4 incompatibility issue (prior to this, the extension has worked perfectly well with FF4).

I've noticed though that the taglist has been getting into a bad state, where nothing will show up in autocomplete until you manually go in to the extension options, clear the taglist, and reload it.

My best guess is that perhaps the extension is hitting failboorus when it goes to update automatically, and that somehow screws things up.

It's most likely a danbooru issue not a danbooruup issue, my copy that runs exclusively on 3db is working fine. Over here everything's gone wonky; aliases have been failing, things have been running slowly, the fastfav thing undid itself.

Shinjidude said:
My best guess is that perhaps the extension is hitting failboorus when it goes to update automatically, and that somehow screws things up.

That sounds plausible.

It would help with the debugging if someone could send me their broken danbooruhistory_z.sqlite file. (Delete your tag history first.)

1 2 3 4 5 6 7 8 9 12