[OUTDATED] ★ Tetra's CSS Guide ★

@Ashlynn

I don't understand what you mean by "it won't let me" - What part are you stuck on?

Whenever I put my cursor over the post the magnifying glass isn't there and won't let me zoom in :)

@Ashlynn

Right-click on the image inside the post and click "Open image in new tab" (or "View image" if you are using Firefox). This should take you to a page that just has the image. The browser should let you use the magnifying glass to zoom in.

This works only if the image is bigger than your browser window or container. If the image is at its full pixel-perfect size, there will be no zoom option available.

Hi there. I'm an amateur coder and I work with HTML and some CSS.
If you had a moment, I was wondering if you could maybe answer a quick question?

--

Does Wolvden not let you type directly on top of pictures?
When I am typing my code, I get this result, which exactly what I want:

But when I input the same exact code into wolvden (I edited the container to fit since wolvden messes with those) and it looked good in the post editor. But when I posted, I ended up with the text and image separated:

I am still very unaccustomed to coding on Wolvden, and I've found that many of my HTML and CSS code does not seem to work the same on WD as it does everywhere else. I was wondering if you maybe had a  solution to this?

I know I could do one large table and get the same similar look, but on WD my rbg transparency for table backgrounds does not work, and if I have an image background on a table, I have to re-paste the code each time I edit, so I was working on a work-around. Turns out this 'work-around' seems to be causing me trouble as well. 

Thank you either way.  :)

@Spibs

I have some bad news and good news about your inquiry:

The big issue with Wolvden's code editor is its purifying system which, in addition to not allowing certain HTML elements such as divs and style tags, is very unreasonably finicky with some styles. So until an overhaul of the system we're pretty much stuck with some of the annoying errors such as the disappearing background image.

I can at least share this tip to mitigate the frustration of the disappearing background:  Right before saving the post, I copy/paste all the code I have into a separate text file on Notepad, and save that file as well. Whenever I need to make changes to the post, I hit edit post, then copy/paste everything from the text file back onto the post editor so that everything still works as before. Repeat with each time I'm saving changes - before saving edits, copy/paste the entire code into a text file and save it.

My good news is that you can put text over a background with semitransparency: example here, with code! Unfortunately this requires some table wrangling but the end result is hopefully what you were looking for.

@ tεtra

Thank you so much.

I do the same thing with tables, except I use GitHub gists. I was trying to find a workaround because it's just annoying haha.
The code copying and re-pasting works, but it definitely gets a bit... [I'm not sure of English translation] langweilig? 

Ah yes, I was looking for that. I was missing a few pieces to make it work here on WD. It is typically not as complicated when I am working with code regularly XD
The end result is what I am going for, just a bit different way than I had been going about it. But if it works, it works :)

I got a question. I can't figure out how to change the white and the blueish-green. Am I missing something or I might be looking over it in the code?

@Dragoness

The blue bar should be the selector name .subheader, and the gray bars should be tr:nth-of-type(odd)

You can change these colors using the background property. tr:nth-of-type(odd) is a 'stubborn' one so be sure to use !important

I will be using this guide :0

I have a small, yet quick, question.

I was wanting to add a custom cursor to my den page (I wanted to add-on to CSS I currently have, which is premade by Katie) and am not figuring out how to get the cursor code to work. Is there any way that I can fix this?