Upcoming changes to CSS code usage: Allowable and unallowable inline code
-
-
I’m glad to see that there are a few more positive responses now. Before Adam posted, it seemed like everybody except Andrew had something negative to say about WordPress.com’s support. In my experience, WP.com provides the best support of any free blogging service. The active forums and quick-replying staff are a testament to that.
Returning to the topic, for the past two days, I’ve begun trying out different CSS attributes to see which ones are likely to be abused and stripped out. I asked for help from one of my friends, who’s more skilled at using CSS than I am, and he sent me some code that he found on a site that teaches people how to use inline CSS on WP.com. Surprisingly, I found the code to all be pretty unastounding. The only attribute I found that normal people would probably not need to use inline is
style='z-index:number;'
The rest all seem to do pretty basic stuff: making text bigger and smaller, changing their font and color, adding a space above some text, wrapping text around the sides of pictures… They’re code that aren’t likely to be candidates for being stripped out. Maybe it’s because I’m don’t use that much inline CSS anyway, or that don’t know how to use it in a “tricky” manner, but these attributes seem to do only basic, unremarkable stuff that can’t be used to alter the themes. There don’t seem, to me at least, to be many ways to abuse them. So maybe the upcoming changes aren’t going to be as big of a deal as I thought, since few attributes seem worthy of removal.Until we get some more definitive answers about what will stay and go, I’m curious to hear what code other people think are being used to get around the CSS restrictions. Maybe in the mean time, we can develop our own list of candidates that will likely be stripped out in the upcoming changes.
Thank you, tellyworth, for sharing what you know. It’s good to see some confirmation that the basic styling attributes will likely remain, which is pretty much what I concluded from my experimentation with that sort of code.
I agree with Andrew and Adam that some of the “abuse” is likely coming from users who are trying to bend the rules and find ways to use the custom CSS features without paying for it. Maybe those users aren’t aware that this hurts WP.com, both financially and by creating a community of haves-and-have-nots using unscrupulous means. But, I think I might know of the physically malicious, damaging uses that tellyworth is mentioning. It might have to do with the two attributes I’ve previously highlighted for removal, and possibly a third. Like tellyworth and Adam have said, it’s probably not wise to talk about it here, in case somebody tries to have some “fun” before the changes go into place.
-
-
-
Not to worry. We all make mistakes. In fact I’m quite accomplished at doing so at least once or twice every day. :D
-
Worried with the “loophole”, “bad guys” and “bad things”, security or financially …
Let us (not upgraded to CSS edition) change font family, size and color, and many other things that don’t damage security and/or financially!
(Sorry for this writing, without any kind of dictionary) -
-
@ludusnaturae
I am likewise worried but I’m trying to remain optimistic that the final decision will not be to remove the ability to use inline CSS for minor style and color changes that do not threaten security. A forum search will evidence the fact that I was the Volunteer who drew Staff attention to using inline CSS to redirect visitors to other sites (linked from the header image) could be problematic.I have been a wordpress fan for years and will likely remain one, but I tell you that it’s very hard to explain to those who have come from Blogger where they do not have to pay to make background color and font changes and can do so with a click of a button that they have to pay to do that here, and then do the work required, as well as renewing payment every year.
Blogger also introduced a brand new Template Designer on March 11, 2010 featuring:
- 15 new, highly-customizable templates, split into four families: Simple, Picture Window, Awesome Inc, and Watermark
- One-, two-, and three-column layouts for each template, with complete control over the size and arrangement of the columns
See > http://bloggerindraft.blogspot.com/2010/03/blogger-template-designer.html
It’s hard not to feel envious and difficult to take the ribbing contrasting what’s available free of charge that I’m getting for being a wordpress.com fan girl. :(
-
Congratulations for Blogger users!
But I will stay down in WordPress, me and us (in another blog), with more or less HTML available.
I (we) have a lot of reasons to choose WordPress (…).
I (we) will likely remain WordPress fan, too. -
https://en.forums.wordpress.com/topic/about-background-colour?replies=27#post-451129
As of now, on blogs that don’t have the CSS upgrade we will strip the “position” property on save. That means you can keep your existing CSS in posts or widgets, but the next time you save it, it runs through the new filter and the “position” property will be lost.
- The topic ‘Upcoming changes to CSS code usage: Allowable and unallowable inline code’ is closed to new replies.
WordPress.com Forums 