This is for the Dev since I noticed that there were changes made to the report queue:1) In .report-controls you're setting the display to flex but you don't seem to know what flexbox is capable of (https://css-tricks.com/snippets/css/a-guide-to-flexbox/). What do I mean by this? I mean that there's no reason to give the clear button margin-right: auto !important when flexbox is perfectly capable of keeping the clear button away from the BR button. The same goes for the other margins on the buttons since gap: is perfectly capable of automatically setting those for you without you having to say that buttons have a 2px horizontal margins. display: flex actually means that you're using the default values for flexbox (row, nowrap, flex-start, etc.) without actually knowing that you can change some of those and thus not need to use margins to do what you're trying to do. Simply putting each group of buttons into their own separate divs and then using justify-content: space-between to put each div at opposite ends of the report yields the same results without having to use margins. The same can be said for centering the buttons without having to use padding.2) From a UI standpoint this is actually worse than before because the smaller and closer together the buttons are the easier it is to make mistakes due to miss clicks. Particularly the File Deletion button is only 20 x 25px which is pretty small and on top of that it has a 1px margin with the Delete button. Having 4 or 5px wide gaps between the buttons doesn't impact the aesthetics at all and makes everything less prone to mistakes. The same can be said for putting the full words back in rather than shorthands. Functionality is way more important than fancy 1px shadows killing posts that only needed file deletion.3) The Delete button has no mouse hover labels and the BR button uses the browser built in labels rather than the custom black ones that the File and Clear buttons have.
Also for mobile point 2 is even more important, the buttons are extremely small and not having more space to click them is really not helpful.
MAKE THE FUCKING BUTTONS BIGGER WTF I'M NOT A VALORANT ZOOMER I CAN'T SNAP 360 FLICKS ON THESE
Seconding the buttons being too smallAnd the clear being too close to the delete buttons
>>9227am I a brainlet I didn't notice anything was different
>>9232yeah
oh god oh fuck what is going on with the buttons ahhhhhhhhhh
Its CSS, a few !importants jammed into divs unnecessarily won't tank the framerate of the janny queue.
I agree that there probably should be a rethinking of how the clear button strike zone is so close to the delete/file delete. Its not uncommon to go on a clearing spree and send something innocent into the shadow realm, causing the thread to go into a schizo tangent about the janitor's abused childhood
>>9236doubly, nay, trebly so for mobile jannyings
The buttons being small got me to finally start trying keyboard shortcuts.
just make everything one button and it spins a wheel of fortune for what happens to the post
>>9239>just make everything one button
I feel like having a template as heavy as ban evasion under the quick ban menu is a little dangerousPerhaps there should be an additional prompt that pops up to avoid missclicks?
Btw, the new quick ban pop-up doesn't inform you if a post has pendings so it's a surefire way to stack requests. I also agree with the GR9, it's not used that often and it can be 99% of the time be substituted for other rules.
>>9227You are hired as 4chan's dev. (no pay btw)
>>9241>>9242isn't gr9 one of the most common bans?
>>9244I think this varies wildly depending on the board. But GR9 really should stay as an option for quick BR
>>9242this is my biggest concern desu
>>9230I can't help but notice you aren't using HPH. Report to my office for disciplinary action immediately.
>>9229skill issue
the more pressing issue for us opressed phone jannies is that in the 'view' screen when u click on a number to bring up a preview of that post/reply 95% of the time the preview is clipped off of the screen.this has been a thing for as long as i have been a janny u.u@dev
>>9253True, hate that shit.
I like the new quick BR thingy but it doesn't show pending BRs so I unintentionally stacked the first time I used it.
>>9256holy shit thats a really good point i never even thought of that.im probably never going to use it now lol.
>>9240>if a janitor sees a ban request panel you've screwed up
>>9256>it doesn't show pending BRs so I unintentionally stackedThey're setting us up to fail.
>>9242This actually makes jannying harder when you can't see if you are stacking wrs/brs.
>>9242>>9244>>9245It's probably very board dependent, on some days GR9 is 90% of the BRs I submit.It might be too difficult to implement, but if we could "pin" some BRs that we individually use frequently then we can customise it to our liking rather than having a generic list for all jannies. This would also avoid any "bias" that having a pre-configured list might give us, e.g. "these BRs are suggested so I should be using them more" kind of thinking.
>>9264nice suggested feature, pull requests are open buddy (they aren't)
>>9264more realistically, you can write a tiny custom CSS rule to block out the quick ban options you dont want to touch.
>>9266As the HTML is currently written, custom CSS would not be able to do that.
nonsense. Here's if you want to hide GR9 quickbansdiv[data-cmd*="quick-ban"]:last-child { display: none;}
>>9268I kneel.
>>9227devfags, please take noteif you're going to intro a "quick BR" button, kindly allow the following options for janitors- warn request toggle- pending requests notifierthank you for your consideration, oh glorious ones
I like the quick BR, even if people have noted there are some problems with it, however one complaint:On /pol/, BRs for racism are inapplicable, yet "Global Rule 3: Racism" is in the quick report selection. And by "inapplicable" I mean "not present in the regular BR menu". This either needs to be replaced or removed.A quick WR would be cool too. Stuff like "Warn for Off Topic" or "Warn for Sage".
>>9270Seconding this.
>>9270>warn request toggleI don't think this is a good idea. It's a "quick BR" menu. If you need to do something more involved than BRing something for off-topic, NWS, racism, evasion, etc, just pull up the BR menu. If you try to overextend a feature, it quickly loses its usefulness because it becomes just as complex as the thing it's meant to replace.Pending requests notifier feels absolutely necessary, >though.
>>9275>press one key to turn from BR to WRtell me how this doesn't save time
>>9276Ctrl+click for warn would be cool
>>9242>I also agree with the GR9>it's not used that often and it can be 99% of the time be substituted for other rules
