![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Removing lj* classes
Oct. 14th, 2009 09:30 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
wyntarvoxThere are a still a few CSS classes in core2 that use the lj prefix (ljtaglist, ljedittime, ljuser and ljcmtmanage). foxfirefey and I talked about it briefly in IRC and she mentioned that it had been discussed before, but I think these should be stripped out and replaced with non-site-specific classes.
As far as I understand it, the argument against changing them is that it could mess with users' existing custom CSS, which is definitely a very good point. However, I think given enough warning and follow-up support, we could make this change now without too much disruption. It wouldn't really be that difficult for users who are affected to adjust their CSS to the new version, especially if we're very clear about exactly what changes we're making.
If we want to change them, we're obviously better off doing it sooner rather than later. The longer we leave it, the more users whose custom CSS we may be messing with. Whichever way it goes, I think we need to make a final decision ASAP so we can either get on with fixing it or have a final decision made to not fix it.
Thoughts? Comments? Rotten fruit?
foxfirefey and I talked about it briefly in IRC and she mentioned that it had been discussed before, but I think these should be stripped out and replaced with non-site-specific classes.As far as I understand it, the argument against changing them is that it could mess with users' existing custom CSS, which is definitely a very good point. However, I think given enough warning and follow-up support, we could make this change now without too much disruption. It wouldn't really be that difficult for users who are affected to adjust their CSS to the new version, especially if we're very clear about exactly what changes we're making.
If we want to change them, we're obviously better off doing it sooner rather than later. The longer we leave it, the more users whose custom CSS we may be messing with. Whichever way it goes, I think we need to make a final decision ASAP so we can either get on with fixing it or have a final decision made to not fix it.
Thoughts? Comments? Rotten fruit?