Hey, thanks for the help with the blocking situation. I calmed down and used the advice given from the thread to contact the admin and looks like everything is going to be alright, I won't need to start another thread. However thanks for telling me how!
Could you give an example where I am not responding to someone else's necro post?
Yes, having an auto lock would help; in fact, there is a script for it in the FANDOM Open Source Library (I think). However, necro posting is not inherently bad. What is bad is necro posting for no significant reason; like commenting "I agree!".
Sometimes, necro posting occurs simply because new users don't know any better. The most common form I have seen is that they have a question that is only somewhat related to the original topic and just post at the end thinking that a thread is for an entire topic rather than a specific issue. Another common reason is that they have the same issue but don't realize that the cause and/or solution may have changed if the original post was made a while ago.
There are some good reasons for necro posting. For example, if you know the same bug is happening again or if there is critical new information that should be shared with future readers. When I say critical, I don't mean something like "I cleared my cookies and it works."; I mean something like "This extension has been disabled due to security concerns.". Although, the latter case is rarely done as most users have better things to do with their time than comb through thousands of old threads just to provide updates; especially when it is very likely no one is even reading the thread.
Because there can be legitimate reasons for necro posting, I don't think threads should be auto locked be default. Of course, as with anything, if a particular wiki is having a significant problem with a lot of unnecessary necro posting, then sure, they could consider doing it.
Good news, the infobox design has been finalised, the mixed border outer gradient is present as well! For what it’s worth, please accept my sincere thanks for all your help in creating the mixed colour main page headings and the CSS for the rest of the site in our commendable thread. You may always admire your very impressive handiwork on the Ten Count wiki! The even better news is I’ve found the perfect site to use the second CSS design developed, namely the initial curved border appearance, so that's even more promising developments, thanks again!
It is indeed! And no way don’t think that at all, it was really nice that you even considered helping to begin with. Not to mention sticking with it since it was quite the marathon, one so worth it of course since it’s the best design ever!
As for the final touches of the “Previous” “Next” tabs, both their padding and the outer mixed border gradient, that’s all in the Ten Count CSS here. Also turns out there’s no longer a need for a backup border in case it doesn’t show on certain browsers (this was a helpful page that shows which search engines can display the appearance, of which they now all do). Also the Wikia CSS is being favoured over the Commons one for the future, which is even handier since that one is accessible from the Admin dashboard. I’m now also so helpful!
Yes, I have found that site helpful as well. My point about having a fallback was just incase someone doesn't have the latest version. But you are correct, all the latest browsers, even IE, can handle the gradients without issue.
Regarding Wikia.css v. Common.css, that has to do with how CSS used to work. However, the distinction is practically non-existent at this point.