Yeah commas (and /*comments*/) were recently added, probably six months back or so. I think a few other things were added around that time, like
But yeah, the dA CSS has changed a bit over the years
I just like adding a tab before the selector since it lets me easily see the "stuff I could change", since I format it the way I do. Doing things all in one line (
:before/:after and maybe content:?But yeah, the dA CSS has changed a bit over the years
I just like adding a tab before the selector since it lets me easily see the "stuff I could change", since I format it the way I do. Doing things all in one line (
h1 {color:blue;}) just seems rather uncoordinated, especially if you have a lot of properties 
Oh I write out like:
h1{
color:#ffffff;
}
Except if there is only display:none; since no other code will be needed there. One line... I can understand writing it out in one line if it is the HTML for a div style or something, which would be excessive to have it all written out. But everyone writes it in their own way. I guess the industry standard is to do it like dreamweaver with the tab in there.
I can't remember when I decided to randomly try the commas again, about 6 months ago sounds right. I remember the roll out of content/before/after. But didn't know what else was released.
I never really used comments, but I suppose it would be good to add to make my skins editable by the users (more easily). Since I do a lot of them as commissions where the user has little to no knowledge of CSS typically. Thanks for the heads up.
h1{
color:#ffffff;
}
Except if there is only display:none; since no other code will be needed there. One line... I can understand writing it out in one line if it is the HTML for a div style or something, which would be excessive to have it all written out. But everyone writes it in their own way. I guess the industry standard is to do it like dreamweaver with the tab in there.
I can't remember when I decided to randomly try the commas again, about 6 months ago sounds right. I remember the roll out of content/before/after. But didn't know what else was released.
I never really used comments, but I suppose it would be good to add to make my skins editable by the users (more easily). Since I do a lot of them as commissions where the user has little to no knowledge of CSS typically. Thanks for the heads up.
Heh, yeah I never released any CSS journal templates, mostly since I don't want to be bombarded with questions about how to do X or how to do Y 
That's sort of the reason why I don't release any GM *.user.js scripts anymore; I don't want to be bothered by people when the script doesn't work like they want it to or doesn't work anymore since dA changed shit.
I mean, I love that people release journal templates/skins, but it just seems that it's never a case of "thanks for the skin", more it's a "how can I change this thing?", which would just annoy me. Install the skin and be happy, or if you want to change it, then learn CSS
That's sort of the reason why I don't release any GM *.user.js scripts anymore; I don't want to be bothered by people when the script doesn't work like they want it to or doesn't work anymore since dA changed shit.
I mean, I love that people release journal templates/skins, but it just seems that it's never a case of "thanks for the skin", more it's a "how can I change this thing?", which would just annoy me. Install the skin and be happy, or if you want to change it, then learn CSS
I guess it is a balance of that. I get a lot of thank you's and a lot of people who want to know how to do something. I bombard them with too much information 
Which I do warn people about on my front page. If they ask me a question, they should expect to get ANSWERED (in triplicate).
I don't mind explaining things, as teaching someone else something helps me learn it better.
Which I do warn people about on my front page. If they ask me a question, they should expect to get ANSWERED (in triplicate).I don't mind explaining things, as teaching someone else something helps me learn it better.