It was closed and re-opened a few times (full revision history:
http://programmers.stackexchange.com/posts/46716/revisions).
Every time that question got shared somewhere, it started getting crap answers instantly, everyone ignored the fantastic community curated top voted answer and went ahead and added yet another one liner saying "learn css".
No one wants that question closed, but at the same time only a handful of people actively prune it every now and then. Right now it's open, but if it starts generating crap answers yet again, we might close it. And then silently re-open it when no one's looking, hoping that the next troll that visits the site won't notice.
However, keep in mind closed doesn't mean dead, we have lots of great (but closed) questions (http://programmers.stackexchange.com/search?tab=votes&q=...), if at some point a question becomes incredibly troublesome, closing it is the easy - and reversible - fix. Killing crap answers, rewording the question to be a bit more specific, etc, is a very slow process, but it happens.
No one wants that question closed, but at the same time only a handful of people actively prune it every now and then. Right now it's open, but if it starts generating crap answers yet again, we might close it. And then silently re-open it when no one's looking, hoping that the next troll that visits the site won't notice.
However, keep in mind closed doesn't mean dead, we have lots of great (but closed) questions (http://programmers.stackexchange.com/search?tab=votes&q=...), if at some point a question becomes incredibly troublesome, closing it is the easy - and reversible - fix. Killing crap answers, rewording the question to be a bit more specific, etc, is a very slow process, but it happens.