>>1271435
const insertAfterConfigNode = document.getElementById('settingsMenu').querySelector('.panelContents:last-child #settings-SGlnaGxpZ2h0IG93biBwb3N0cyBhbmQgcG9zdHMgcXVvdGluZyB5b3').parentNode;
[code]
just a heads up, that will break whenever the site updates because I fixed the capitalization of the settings and that key is the label text converted to base64 (don't ask)
[code] const spoilerLbl = document.createElement('lable');
intentional? french canadian? not that this site's great on accessibility, but should probably use the right tag
const lbl = document.querySelector("#quick-reply .spoilerCheckbox[for=qralwaysUseBypassCheckBox]");
this will also probably break at some point, because that checkbox actually does literally nothing and should be removed
.style.display = [...]
this could cause weird things if the posts get remodeled
it's more resilient to add/remove/toggle .hidden { display: none; } from global.css and let them retain their styling, whatever it may be
>thread.refreshParameters
>thread.refreshCallback
these will break update after next (hopefully)
all of the thread updating is rewritten and there will be an event you can listen to instead
I'll try to remember to give a heads up when that rolls around
interesting idea overall
another way you could trigger that instead of using the subject is using [board] or [aa] tags, either empty which will just be an empty span inserted or with a key and remove/hide the span they create before the post gets rendered
aa prevents formatting inside it and almost no one uses it normally