Posted under Bugs & Features
nonamethanks said:
CTRL+Enter has always worked. The change is the deprecation of the enter key being pressed alone, which will be done in phases.
I see.
nonamethanks said:
BTW the tab key works too to select autocomplete entries.
But it looks like it's only able to take the first suggestion? Which isn't useful for me.
Thx for the answer.
DeadW@nderer said:
Today I noticed new design changes for commenting sections - I sorta welcome these, but new quotes are blending with replies for me, just saying.
I honestly thought at first I was looking as downvoted stuff as the gray was actually hard to read.
Not sure if I'm a fan of the new searchbox behavior. I liked having my recent searches still showing up in the autobox. Right now it's really distracting to see the giant pile of "Suggested Tags" popping up and desktop. Especially when the first things that show up when I type in t is "tits" in the dropdown box instead of 'touhou' which was what I used before and I'm like come on man. Is that the autocomplete thing people talking about? (Also using custom CSS isn't really a fix IMO and effectively telling people to screw off and shutting them down by going "Just use custom CSS")
I've got no clue what the hell I'd be seeing on tablet which worries me that overall functionality in both landscape and portrait layout will be hurt by this.
Unbreakable said:
Force changing everyone's comment threshold was very rude to be honest, but the showing of comment score is very useful, it's something that's been missing for a long while.
Edit: With comments
I'm not sure why we need to be informed about deleted comments existing on posts though.
I'm honestly not a fan of either change as I get a feeling this will start people on the path of "like/karma farming" with comments aiming to get highest score than say anything of value.
Updated
Zelinkokitsune said:
I'm honestly not a fan of either change as I get a feeling this will start people on the path of "like/karma farming" with comments aiming to get highest score than say anything of value.
That's already happening though with people saying witty comments and puns.
MaskedAvenger said:
Tried the CSS one. Didn't work. BTW, how does one insert custom Javascript?
There's should be an icon on the top bar now.
Ctrl + S or using the File menu underneath the Editor tab.
As for the navbar, it works, but as a side effect, when viewing a post that is part of a pool, the navbar is not showing, in effect hiding the name of the pool.
Oh, sorry, I thought you didn't like the bar as a whole. If you only want to hide the sequential navigation then use the following CSS instead.
#c-posts #a-show .search-navbar {
display: none;
}Updated
Zelinkokitsune said:
Not sure if I'm a fan of the new searchbox behavior. I liked having my recent searches still showing up in the autobox. Right now it's really distracting to see the giant pile of "Suggested Tags" popping up and desktop. Especially when the first things that show up when I type in t is "tits" in the dropdown box instead of 'touhou' which was what I used before and I'm like come on man. Is that the autocomplete thing people talking about? (Also using custom CSS isn't really a fix IMO and effectively telling people to screw off and shutting them down by going "Just use custom CSS")
Yes, this is autocomplete. This is how the searchbox has worked for the past 7 years. In that time, only ~350 people ever disabled it. Half of whom no longer use the site. It was removed because yes, I don't want to support configurations that few people use.
The main reason this option was originally added was because, at the time, there was a Firefox extension called DanbooruUp that added autocomplete to Danbooru, and Danbooru's native autocomplete conflicted with it. But that extension has been dead and irrelevant for years. As I discussed above, I'm getting rid of options that only exist for legacy reasons.
evazion said:
Yes, this is autocomplete. This is how the searchbox has worked for the past 7 years. In that time, only ~350 people ever disabled it. Half of whom no longer use the site. It was removed because yes, I don't want to support configurations that few people use.
The main reason this option was originally added was because, at the time, there was a Firefox extension called DanbooruUp that added autocomplete to Danbooru, and Danbooru's native autocomplete conflicted with it. But that extension has been dead and irrelevant for years. As I discussed above, I'm getting rid of options that only exist for legacy reasons.
It hasn't for me it's always been just a generic textbox and I've not changed any options to my knowledge. Honestly a major downgrade IMO as it's making my doing searches far far more annoying.
MaskedAvenger said:
Tried the CSS one. Didn't work. BTW, how does one insert custom Javascript?
As for the navbar, it works, but as a side effect, when viewing a post that is part of a pool, the navbar is not showing, in effect hiding the name of the pool.
Can confirm CSS fix doesn't work. Having to install a janky Tampermonkey script to fix base functionality is a bad thing
Zelinkokitsune said:
It hasn't for me it's always been just a generic textbox and I've not changed any options to my knowledge. Honestly a major downgrade IMO as it's making my doing searches far far more annoying.
The best suggestion i can give you is to get used to it.
Once you do, it's genuinely not bad - you may even discover new tags.
I can see why you would be annoyed, but autocomplete is a very useful tool.
Regarding the recent searches thing, if you want to search for "touhou" search for "to" instead of "t". Of course single-character searches will bring disappointing results.
Comments changes all look and feel great; enabling upvoting your own comments seems like an overall beneficial change when you weigh the pros/cons, too. Will the voting arrows beside the post's score (under Information) also be changed to match comments, i.e. with the selected vote button remaining highlighted rather than the arrows changing to (undo vote)?
Updated
Username_Hidden said:
The best suggestion i can give you is to get used to it.
Once you do, it's genuinely not bad - you may even discover new tags.
I can see why you would be annoyed, but autocomplete is a very useful tool.Regarding the recent searches thing, if you want to search for "touhou" search for "to" instead of "t". Of course single-character searches will bring disappointing results.
When you're searching for more niche tags this is worse than before as previous behavior just remembered my searches like a regular dropdown box meaning I didn't have to deal with that kind of bullshit. I'm not searching for "new tags" I already know what tags I want even though the fact Danbooru's utterly random with "Follow localization" or "Ignore localization" with associations being even more random doesn't help either
Old behavior just got me what I wanted to see as autocomplete doesn't help with 'fuzzy' searches especially when playing Localization Roulette
I agree that the removal of disabling autocomplete is a dismaying change. I had my most commonly searched tags show up in the drop down menu in order of most searched, and while the Tampermonkey script stops the autocomplete, my drop down menu did not return when I tried it.
Personally I go to the Tags section if I have a reason to explore new tags, mostly when I need a drawing reference, and otherwise I stick to my handful of usual tags.
kdakze said:
Why was the keyboard shortcuts setting removed?
From commit 99d4472:
Remove the enable_post_navigation option. This option was originally added to disable the next/prev post navbar beneath posts. It was later repurposed to disable keyboard shortcuts.
Users who don't want keyboard shortcuts are advised to not press random buttons on the keyboard like a caveman.
Only ~1200 users disabled this option and only ~600 were seen in the last year.
kdakze said:
Why was the keyboard shortcuts setting removed?
Because few people used it and it was broken. It didn't disable all shortcuts. It didn't disable autocomplete shortcuts (the arrow keys and tab/enter), and it didn't disable using the escape key to close dialog boxes.
Of course, if these bugs were fixed and it really did disable all shortcuts, I'm sure people would complain about autocomplete being unusable, when in fact they broke it themselves by intentionally disabling keyboard shortcuts. Which raises the question of why have an option that is known to make other features unusable.
Another problem was that certain things are only accessible with keyboard shortcuts. The tag script feature (help:tag scripts) uses the number keys to switch tag scripts, which can only be done with keyboard shortcuts (which isn't great design, but that's how it's always worked).
So it comes down to a question of "Why support an option that few people use, that is known to be broken, and that fixing will just make other functionality unusable?" This is a good example of how something that sounds trivial, like disabling shortcuts, has more considerations than you would think.
