I was bored, so i've made a simple dark theme userstyle.
Changes >Now background is dark duh
>Most of the formatting is the same or similar.
>Inverted the image on the main page to fit the theme.
>Made the tables better in log and stats
>Made the posts in the catalog bigger and removed the scrollbars(so i can finally scroll in the catalog without getting stuck)
>Made the default size for the postform bigger(so i don't have to resize it every time)
Color coding >Cyan is stuff you can click on.
>Red is titles/topic.
>Yellow is subtitles, replycount and date/time.
>Green is names.
>Purple is hapase/mods.
You're gonna need a userstyle extension to install it, then create new userstyle, paste the code and apply it to nano domain. Hope i didn't forget anything, code follows:
Doesn't work for me.
Like, it's not your code, maybe it isn't supposed to be working with how webserver and my browser are set up.
>Content Security Policy: The page’s settings blocked the loading of a resource at self (“style-src http://nanochancsvnej4vxiidu4fhpchkxffl3mgqypub63xadeetkjttavqd.onion”)
If I disable CSP, I can get it to work, but I don't think that's a good idea.
I use Jewfox 52.9.0 and Stylus extension.
>>3076 uhm yeah nano's CSP header is set to accept styles only from itself, i actually get that error too(Tor Browser 8.0.8 based on Mozilla Firefox 60.6.1esr and also Stylus) but it still works regardless on my end, sorry not sure if i know how to help, it's probably related to the browser configuration though
>>3077 >it's probably related to the browser configuration though
I have everything about CSP set to default, therefore I don't think so.
I also use 1.4.23 Stylus, maybe that's a thing.
Also maybe NoScript messing with it.
That's why this shit is fucking nightmare.
>>3078 My Stylus version is 1.5.3 and i'm using uMatrix with "* * script block" to block scripts for reference i don't have NoScript at all
>That's why this shit is fucking nightmare.
Yeah
>>3079 >Firefox 59 finally fixed this bug so I don't think we should do anything. Users of the older Firefox can install a separate extension that alters CSP.
I think Stylus fucks just decided to not do anything.
I'll see if I can fix this.
Though I don't really know about this in general. It looks that earlier (mine) behavior was actually more sane: if userCSS is not from "self" (which it shouldn't have any problem faking, but still), then CSP should kick in and prevent styling. Not any other way.
>CSP should kick in and prevent styling. Not any other way.
I'm not sure if CSP was developed in regard to extensions, it's useful to avois cross-site attacks etc but for styles if you can see the code it's safe, this seems just like a bug of Stylus.
>I don't think we should do anything
lazy fucks
inb4
>bloat
>cianiggers
It does look pretty small and tame.
Your style is nice BTW. I took the liberty of changing body color to #DDD and input area colors to #EEE though. Why would I have an actual white color in my dark theme, like, WTF.
Glad you solved the problem somehow, even i still get the error until it works i'd rather not install more extensions.
>Why would I have an actual white color in my dark theme, like, WTF.
Yeah, i'm the kind of person that likes high contrast themes with bright colors.
>>3113 Let me tell you that you should disable javascript globally while browsing the Tor Network, preferably using uMatrix, you should probably just use Stylus, anyway is it definitely possible to inject css using javascript, you can use this https://github.com/patcullen/injectCSS to add multiline CSS or use jQuery, or just create a new style element and append the style to it. You can find on stack overfow how to do it.
>>pls do bully
i won't bully you, i'll leave that to pic related
>>3116 CSS bullshit is so powerful.
It can actually invert colors of pictures, AND (re-)colorize them.
I've learned that shit recently when I was trying to make a dark theme (I'm not the OP) and non-inline SVG pictures just wouldn't accept color properties, so I had to resort to that bullshit.
Or, rather, in fact, as soon as I learned it, I actually decided that I should just look some theme up, and I found one. I was looking for a dark theme for Wikipedia LOL.
I think hapase color (capcode) does not apply correctly when hapase posts with email field. Like, it becomes nested into <a> "post-email" tag and it most probably fucks with what was written into style sheet about that. Like, strict hierarchy or something.
Proof: nanochancsvnej4vxiidu4fhpchkxffl3mgqypub63xadeetkjttavqd.onion/pol/3439.html
>>3138 Good catch, really easy to fix luckily.
This should preserve link color and style only the capcode, code follows(i recommend adding it after line 118 under the "Post" section):
Optional update that makes the referees and file link/info bigger(they're too fucking small by default), you can tweak size to your preference, code follows(i recommend adding it after line 139, linenumber includes previous update, under the "Post" section):
>>3140 I have a question.
Isn't it just better to say
span.capcode {
color: #BA68C8;
}
since capcode is used only in one certain place?
I don't know much about CSS, but it's an easy guess that it will just apply the rule globabally for all <span>s named capcode. Isn't it just fine and less prone to bugs like that?
Do you have an autistic urge to write down a page structure like that, or is there some CSS creating tool that made a rule like that for you automatically?
>>3158 Yes he did, you just didn't understand because you're a normalfag brainlet.
<Do you have an autistic urge...
>Autism is the fuel of all good code.
>>3158 >You didn't answer the question
I don't use any tool, yes i like to write a strict hierarchy cause i like it that way(and the nanochan stylesheet itself uses a lot of child combinators).
>you fucking weeb
Chigau onii-chan! Weeb janai >.<
>>3159 I prefer to get an exact direct answer usually.
You may be surprised how wrong you might get after assuming a lot.
>>3162 >I don't use any tool
Shame, I was kinda hoping you did.
Makes sense when dealing with WYSIWYG bullshit.
>cause i like it that way
Imagine hapase changes some ids or overall page structure now.
An unlikely event, but imagine the pain.
>>3166 Since the post referencing was added, Hapase hasn't changed anything except for captcha mechanics, spam filters and other "back end" stuff. I think it's pretty stable for now. Not much to improve except for maybe some minor css things.
>>3166 I'm gonna mantain this theme as long as i use nano(since i use it), if something breaks report it and i'll fix it, with this said you can rewrite and make better the theme however you want(it's not like i've put that much effort in it either).
Hello again fellow darkthemed nanochanners!
Today i come with a reworking of the navbar(i always hated the order of the boards), this come down to my own preference but you can modify everything from the order of the boards to the separators and the message.
Code follows(add after line 25):
So here i am again, so today i was thinking of ending my existence but in the end i decided to update a theme for a board that nobody even uses anymore :D
I'm gonna start with saying that this will probably break some stuff and it's optimized for 1080p screens, report bugs in case.
Anyway i got some new cool features today, first i reworked how catalog worked, now it's all more compact and more information fits, i've hidden the board title and subtitle, the update button(why is that even a thing you have the one on your browser) and i've moved the new thread/new post button in the navbar, plus since now catalog threads are smaller i've added an animation that gets triggered when you hover that will expand the thread showing the entire thread comment inside the catalog(i think this is the best solution between fucking hapase scrollbars everywhere and cropped threads like in previous version), i also removed mod buttons since nobody else than hapase can use them and also a line that was stealing space before the thread comment, i also made minor changes that i'm too tired to remember.
I'm actually really satisfied with this version, i've implemented every feature that i wanted and now i'm out of ideas, i might make a userscript next since you can only do so much with CSS, but nano is kind of dead so that probably won't happen.
Post feedback.
So hapase in all her wisdom deleted /test/ without any warning and that broke the theme, women and tech amirite, anyway i fixed it, note that it will still be broken on old static pages until they get updated, annoying but i can't do much there... i also made the navbar more compact for mobile/small screens.
The theme breaking on UI changes is natural and not really the problem, the real issue are old static pages lingering around after changes, after updating stuff you should regenerate at least all last month html pages and all boards catalogs, look at the mess in /ar/ with the old announcement, it shouldn't be that hard to implement.
I know that i said that i was satisfied with how the catalog worked in v1.1.0 but i had a pretty cool idea today, since v1.1.0 if you hover on a thread in the catalog it will expand showing more information, this is fine but the problem is that since catalog is implemented with flex it moves the next row(sometime out of the screen) and it's annoying, so instead of changing it's size i figured out i just had to make it's position fixed and the flex would rearrange itself, in the end it ended up being kind of like a modal, since the :hover pseudo-class would make the catalog unusable i also changed it to use the :active pseudo-class.
>>3421 >pastebin.com
>Attention Required
Upload it here.
Using a text editor, put "%PDF" in its own line before everything else, and then nanochan will think it's a pdf.
I was bored, so i've made a simple dark theme userstyle.
Changes
>Now background is dark duh
>Most of the formatting is the same or similar.
>Inverted the image on the main page to fit the theme.
>Made the tables better in log and stats
>Made the posts in the catalog bigger and removed the scrollbars(so i can finally scroll in the catalog without getting stuck)
>Made the default size for the postform bigger(so i don't have to resize it every time)
Color coding
>Cyan is stuff you can click on.
>Red is titles/topic.
>Yellow is subtitles, replycount and date/time.
>Green is names.
>Purple is hapase/mods.
You're gonna need a userstyle extension to install it, then create new userstyle, paste the code and apply it to nano domain. Hope i didn't forget anything, code follows: