Timeline for Support for generic CSS and JS issues
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2016 at 4:32 | comment | added | Pieter Goosen |
That is borderline, definitely. I think this was never closed because the issue was resolved using WordPress (using the build in loop counter $current_post*) instead of a generic CSS, and that is the difference. Even when that question cycled through as active when you posted an answer, it never received any close votes (when you get to 3K you will be able to see close votes) so my thought is that the community is happy with the question and the answer and don't see it as generic CSS. But this is just my opinion. If you have issues, you can always post a new question for discussion :-)
|
|
| Jan 5, 2016 at 2:36 | comment | added | jgraup | I'm curious, is this type of post considered generic? wordpress.stackexchange.com/questions/98915/… | |
| Dec 13, 2015 at 6:32 | vote | accept | Pieter Goosen | ||
| Dec 12, 2015 at 17:27 | answer | added | kaiserMod | timeline score: 1 | |
| Dec 11, 2015 at 19:16 | answer | added | Howdy_McGeeMod | timeline score: 7 | |
| Dec 11, 2015 at 11:36 | answer | added | RarstMod | timeline score: 3 | |
| Dec 11, 2015 at 5:49 | history | asked | Pieter Goosen | CC BY-SA 3.0 |