Skip to content
TORNLIFE More

For HTML/CSS Developers - Quick Question

Started by VerbalFox [1732432] on in Questions & Answers.

7 replies · 109 views · thread synced · 3 days ago · View on torn.com
About this thread

Posts archived: 8 / 8 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
8
Discussion span
→
People posting
4
Likes on archived posts
3
Authority score
43 / 100
Historical score
17 / 100
Story score
28 / 100
Engagement score
48 / 100
VerbalFox [1732432]

Looking at profile signatures on torn, I've noticed that you can't add custom CSS to them. (excluding inline CSS, but working with that is a complete pain when you've got a lot of div classes, and I really just don't want to)

Now I can list half a dozen reasons why custom Javascript is a bad idea, but I can't see any risks with allowing custom CSS on a profile signature.

To iterate, I don't know much about CSS, so before I make a tit of myself, can someone explain to me why allowing custom CSS on profiles would be a terrible idea? (Namely through the

(Just to clarify, I don't know with certainty if it's possible to include CSS (again, excluding inline, boo), so if there is a way of doing it, via linking a CSS script or
VerbalFox [1732432]

Figured as much. I really want to start seeing profile sig's that look 2018 as opposed to 2008, but sadly, that can't be done without CSS access.

What would need to be considered by the game designers if they decided to add CSS support in sigs?
Mauk [1494436]

They won't. They are currently working on a new bbcode editor, so even inline css styles won't be possible anymore.

Sites that accept custom css usually work on a whitelist-based approach, parsing the styles and erroring on any disallowed property or value.
AllMight [1878147]

Well CSS is global - which means if you put a css class there it will affect the whole game page.

Ofc they dont want someone to make the whole torn page red for every one visiting his page...
Mauk [1494436]

That could be easily prevented by transforming the source to restrict selectors, though. (not that it matters, since there's no interest in this)