Great job on the update! Still looking around and exploring, but I really appreciate the new Watching section (under Airing) on the homepage. Also, I knew that that font looked familiar - Montserrat, nice choice!

Will do!

Wow, this is great! I've been waiting excitedly for this to be released and it's finally here.

Thank you to all the developers who put their efforts into this, I know how hard it can be to get code working. Looking forward to future updates, but know that you've got my full support!

Thanks for the reply, looking forward to it!

Oh, of course! That's why targetting just h3 before wasn't working, the #lists h3 property was overriding it.

I agree, that's a cleaner way of approaching it.

Yep, I saw your EDIT. Thanks!

I didn't think lack of spaces would cause any problems (I hadn't used any for the other headers). However, I added spaces like you suggested and it still doesn't seem to be working.

Perhaps the rest of my CSS is causing a conflict? Here's my current code:

EDIT: I just saw your edit! The code you gave me works wonderfully. Thank you so much!

Good suggestion!

Hmm, I tried doing div[id='plan to watch']>h3 { color: #FFFFFF; }, but it doesn't seem to be working. Am I doing this correctly?

Thanks for the quick reply!

Ah, I see! The bit about the 'Status' column makes sense, your CSS worked great, thank you.

Unfortunately, my 'Plan To Watch' header is still not displaying the color that I'd like it to have. Do you mean to say that I can modify an id's name through CSS?

EDIT: First problem resolved thanks to haganbmj.

Hi!

First off, thanks for the thread, it's very useful. :D

On to my questions:

(1) I would like to modify the styling of the "Plan to Watch" header of my list. I tried targetting the h3s specifically at first, but for some reason that doesn't work. So instead I targetted each section's id and then its child h3, however, the id for "Plan to Watch" is id="plan to watch"; IIRC, this is invalid HTML (some hyphens between each word would solve this nicely; id="plan-to-watch") and only works if you're trying to define multiple classes (and not ids). Am I mistaken? Is there any way to modify this header without doing it this way?

(2) A minor issue, but it seems like I have a visual bug in the th of some of my sections.. the Progress of each item some sections is stretching the table further than it should (?). Just want to know if this is happening for other users, too.

Thanks in advance! :)

Thanks for the tip about the unique selectors! I have a similar problem with the shared #completed; I want to hide my Completed list without affecting my Custom Lists.

Bugs:

Type of Bug: User Settings
Summary of the Bug: When I go to change my display name in Settings > User, and my new display name is unavailable to be used, instead of throwing an error it updates my name but with 'HTTP/1.0 403 ForbiddenCache-Control: no-cacheC'
Reproduction Steps: Settings > User > Edit Display Name > Enter Current Password > Save
Reproduction Rate: 100%
Browser: Google Chrome

Feedback:

I've been tinkering around with the CSS ever since Anilist 2.0 launched (kudos to the team, by the way! :D), and I've had some minor issues:

It would seem that Custom Lists are now organized under div with id="completed" alongside the default Completed list. I used to be able to hide the Completed list without hiding my Custom Lists by setting display: none; ... not sure if there's another way of doing this; it would be awesome if I could have my 'TV', 'Movies', and 'OVAs & Specials' Custom lists like I used to without the unsorted Completed list in the way.

Also, I'm not the biggest CSS guru, but I've noticed that the h3 for the 'Plan to Watch' list now uses an id="plan to watch" ... I don't think that's valid HTML (spaces only work when defining multiple classes and not ids?); I want to be able to change the styling of that, but my changes aren't going through.

I would really appreciate it if I could get some solutions for these quirks. For the second one, just change the id to be id="plan-to-watch" ?

Again, thanks to the team for the awesome update! And thank you, Morgvus, for this thread.