![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
OY!
LJ have just tweaked their HTML/CSS cleaner, according to the support page. In the process, they drove cart and horses through my carefully hand-crafted S1 style here. It may take come time to sort it out. If anyone can point me at a list of what exactly this new beastie is twitchy about, it could make my life a lot easier; otherwise I'm going to have to reverse-engineer things to work out what is and isn't allowed.
While they have some legitimate concerns* I think they're currently stripping stuff that's pretty harmless. For example, how the hell can
Well, at least it proves that my "graceful degradation" works as intended...
*there are some downright terrifying browser-specific features out there, from the perspective of defending against cross-site scripting attacks.
[edit: there was a post on the subject on![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
lj_maintenance shortly after a wrote this. I think I'll wait a day or two for things to settle down before I attempt to clean up. I mean, it's not like many people read this journal in the native style, rather than via their own LJ-friends view or some other aggregator]
While they have some legitimate concerns* I think they're currently stripping stuff that's pretty harmless. For example, how the hell can
<style type="text/css"> be malicious?Well, at least it proves that my "graceful degradation" works as intended...
*there are some downright terrifying browser-specific features out there, from the perspective of defending against cross-site scripting attacks.
[edit: there was a post on the subject on
lj_maintenance shortly after a wrote this. I think I'll wait a day or two for things to settle down before I attempt to clean up. I mean, it's not like many people read this journal in the native style, rather than via their own LJ-friends view or some other aggregator]
no subject