>>9110 >Improved moderation tools Didn't you already implement marking of already deleted files so mods can see what actually still needs to be cleaned up? Shouldn't you mention that here? Jumping out of thread moderation mode and comparing what posts do and don't still exist was always a pain. >Global/Local Report & Ban modals have been merged When I check global, does it automatically make a local report as well for the purpose of getting the report to more eyes sooner so the problem is cleaned up faster? >Theme loading has been optimized Great. I've noticed sometimes theme changing on multiple tabs will lag behind, and sometimes forever if I don't reload the tab.

>>9113 >Great. I've noticed sometimes theme changing on multiple tabs will lag behind, and sometimes forever if I don't reload the tab. To clarify, this was an old issue, which I believe you fixed just now.

>>9110 Okay, I have some bugs to report. >First pic: Missing spanish translation for "Total max file size" >Second pic: The "Local times" option seems to be broken for new posts in spanish boards

>>9116 >>Second pic: The "Local times" option seems to be broken for new posts in spanish boards It works on my machine.

>>9116 >second pic Same, happened to me. Nanananan

Label on captcha is fucked up

Long posts have this bug

>>9116 >NaN/NaN/NaN Batman?

Gracias por implementar los CSS que surgerì y el Oekaki, estaré probandolos para reportar errores (De hecho, en el de Evita no tiene fondo)

>>9113 >Posts Marked Deleted Forgotto add that to the changelog since it happened so long ago. I'll add that now. Forgot a couple other things, too. >Does it automatically make a local report Not yet, but this ia stepping stone. I've got ideas to minimize friction when making reports. >>9116 >>9122 Local Times in Spanish is being worked on. Other labels should be fixed already. >>9126 Forgot to credit you and mention the theme in the changelog. Updated that.

Custom CSS isn't working. With "Default CSS" selected, it displays the custom CSS for a second, then changes to Yotsuba B. If one of the other themes in the dropdown is selected, it'll again show the custom CSS for a second, then display the selected theme. If you then re-select "Default CSS", it'll show the custom CSS properly until you change pages or refresh. Another issue, that existed since well before this update, is that if "Default CSS" was selected, Yotsuba B would display for a second before the custom CSS. Now it's the inverse, until you re-select "Default CSS" from another theme, then this original issue returns. Much more minor, but hard on the eyes for a different brighter theme to flash with every new page. Re-uploaded the same CSS, same issue. Other boards seem affected too.

>>9127 >I've got ideas to minimize friction when making reports. Please tell me one of them is attaching reports to your bypass captcha. There's no reason to fill out a captcha for every single report and it's incredibly tedious when dealing with IP hoppers. If you're worried about spam reports, shouldn't the same stopgap that stops regular spam posts stop spam reports?

>>9110 I don't know if it happens to anyone else, but in the sidebar of the mobile version there are some labels without text. I leave screenshots with the normal and spanish version for you to compare. The overlapping text is due to the resolution of my phone's screen and has occurred since the previous update* (when the sidebars were added), but it should be able to be fixed by modifying this in the global CSS (the + sign at the beginning of the line is what needs to be added and the - what needs to be changed): #hamburger-menu-icon #sidebar-menu { visibility: hidden; position: fixed; top: 0; left: -220px; width: 220px; height: 100%; background: var(--contrast-color); border-right: 2px; border-color: var(--border-color); transition: 0.3s; padding: 0px 10px; box-sizing: border-box; z-index: 1000; + overflow-x: auto; } [...] .hamburger-bottom { - position: absolute; + position: initial; bottom: 0; margin: 10px; } * If I didn't report it before, it's because I always forget since I don't usually chan from the phone and this bug hadn't been a big problem until now.

>>9128 Found the problem. The change was merged into master to get a fix on the site in time for holidays, but it didn't make its way back onto the development branch. I've fixed the issue. I think Default CSS is still not behaving correctly since it isn't displaying board themes, but it's an improvement. For now, use Board CSS in the dropdown. >>9129 Yes, that is the plan. We had the idea before of letting users with a bypass skip captchas, but with TABS it should be feasible to roll out. StephenLynx has been really happy with TABS and wants to develop things further. It will take some time to revisit older systems that predate the TABS concept to tie them in, but it should allow regular users to use the site with minimal hassle while blocking spammers, bots, and pedophiles. >>9132 Noted. The mobile layout was never really finished and it might need some love.

>>9133 >Yes, Hallelujah.

Breaking CSS must be this year's April Fools' prank

>>9137 I'm surprised nobody set up an april fools prank

Oekaki doesn't work on firefox 124.0.1 (64-bit).

well that's just fucking irritating

>>9141 addendum, new post transparent too

>>9133 >For now, use Board CSS in the dropdown. That's not working either consistently. It will apply the custom CSS but then it will randomly drop it again.

>>9143 It's being looked into. >>9141 >>9142 Browser and version number?

>>9145 >Browser and version number? Tor. 13.0.13

Something's fucky with my Quick Reply's background. It's pitch black.

>>9153 It seems like a feature

>>9145 Chromium. too lazy to check desktop Also occurs on mobile though (111.0.5563.102)

>>9140 Now it's working. Thank you mods.

Does anyone else have all the icons broken? I'm using Librewolf 124.0.1-1

Board specific CSS themes are fucked They only work after I drop down and select "Board CSS". And only until I load a page, then I have to select "Default CSS" to get them to work.

>>9158 I have a similar problem, in 8chan.moe the icons do not appear, but in 8chan.se it appears as your screenshot in Firefox, Windows 7.

>>9154 Why the hell would making it impossible to read be a feature?

>>9161 You are right, just checked and it's a domain issue.

>>9110 Thank you, admins!

I'm on Firefox Version 123.0.1 (64-bit) for Ubuntu, and I've got the following problems: - clicking a post number does not add a reply link to the "message" field on the post form (but it does open the quick reply window correctly) - hovering over reply links and backlinks for out-of-window posts makes them look like pic related - New posts appended with auto update also appear trashed and transparent

I like this new update.

I'm not sure if these bugs were already reported, but there are missing labels both on the eng.json and spa.json files for text that shows on the mobile version. These are the missing labels: >labelBack >labelGlobalRules

>>9165 Everything seems to work as usual now.

>>9110 Having the Local Times option enabled in the settings, the dates of some posts are displayed as NaN/NaN/NaN (undefined) NaN:NaN:NaN in Spanish boards like >>>/hisparefugio/. I think modifying setLocalTime() in posting.js in this way should solve it provisionally.: posting.setLocalTime = function(time) { var parsedDate = new Date(time.innerText + ' UTC'); if(isNaN(parsedDate)) { // If this condition is met, we assume that the date is in Spanish parsedDate = new Date(time.innerText.replace(/^(\d\d)\/(\d\d)(.+)/g, "$2/$1$3") + ' UTC'); } time.innerText = api.formatDateToDisplay(parsedDate, true); }; But I think it doesn't work very well with some dates. As already reported in >>9244 and >>>/hisparefugio/155421 the "Relative Times" option doesn't work either. In the meantime the local times can be fixed by disabling the homonymous option, pasting the above code in Settings > JS (changing posting.setLocalTime to setLocalTime to make it work) and add this below to run the function every time that the page loads: var createdTimes = document.querySelectorAll(".labelCreated"); for (var i = 0; i<createdTimes.length; i++) { setLocalTime(createdTimes[i]); } Although to be honest, the fact that the boards have different date formats depending on the language does not convince me very much. I think a better solution would be something similar to what chans with Infinity Next has where the user can change the timestamp format as you can see in the attached image. Initially you could make that when loading a page, the timestamps are displayed in the local format according to the language of the system using toLocaleString(). Additionally, an attribute like data-timestamp could be added to the datetime tags, which would contain the real publication timestamp as a Unix epoch time or in some ISO format that would be used to format the date that the user would see (mostly so that this type of functions do not break so easily and/or if there is some userscript that modifies the content of these tags). Finally, and in case an additional option is added to format the date and time as you like, the information from https://www.w3schools.com/jsref/jsref_tolocalestring.asp could be used to display the dates and times in the format of other languages, in addition to https://thdoan.github.io/strftime/ for user-defined formats.