Zorgic it still stands - whitelisting properties/values requires that a parser be manually written to detect allowed values (for security reasons), so it's more than likely that functions aren't currently working.
I basically went through everything on profile pages and noted down what each thing did so it'd be easier to code profiles...! It's just a matter of filling in the blanks. Some code has already been added but you can always remove it. Now with a character pages version!
- (7/11) Added links and stats, rearranged the code to reflect the new order of links in the sidebar; finished characters framework too.
- Added character folders.
I was thinking about what you said
"whitelisting properties/values requires that a parser be manually written to detect allowed values (for security reasons), so it's more than likely that functions aren't currently working."
and that sounds like reinventing the wheel. wouldn't it be simpler to filter the custom CSS input rather than simply putting it up blindly as a style tag? write a simple js that take in the contents of the box as a string, and iterates through the properties, discarding any non-whitelisted properties or values within the property? I mean in that case you could block errors from misspelled properties and generally shorten load times for pages with custom CSS, as well as block certain selectors you don't want modified, like the header of the page that you want to retain the TH LAF.
using a js filter would actually be more secure than the method you're currently using which is capable of generating unforseen errors, since you're rewriting the CSS interpreter. on top of that, posting it automatically has another danger: you assume the only things in the box is CSS
Nice job! I am fairly new so I didnt know which codes this site supported since other websites use different tag s to represent different things