|
> Then there is a single comment (not an answer) which says "you are not supposed to do that", which have received a single upvote. This comment should be deleted as it's blatantly off-topic and a waste of time. OK, let's forget about question one, since I found it in two seconds. > Comments are for asking questions, request clarifications and providing information which does not constitute a regular answer. > Several answers make it clear that the CSS solution is more fragile and worse supported than a JS solution As you say here, the questioning ("clarification") of the question isn't limited to comments. It's easy to mentally ignore comments, but when you have to read through half an answer just to get past the BS... and besides, the CSS solutions in that thread certainly are fragile and bad, but that has nothing to do with CSS being appropriate or not and more because the answers are, well, terrible. CSS is perfectly capable of doing what the question asked for in a robust manner, and it avoids changing the page on-load which is a bad user experience (not that any web developers actually care...) and certainly no less fragile (assuming JS is even turned on in the user's browser). The problem is people telling others what they should do, and I don't want random people trying to dictate what I should be doing -- especially not people giving answers like those. Actually, a couple of the answers are OK, and somewhat explanatory, but the rest are just BS that throw code at you, which is useless and a waste of everyone's time. To be fair, web development answers on SO are the lowest-quality generally speaking. I'm pretty satisfied with using SO for answers about e.g. Emacs. > I really have a hard time seeing the problem here? Uh, seriously? |