| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 3993 |
| 2 | jiangly | 3743 |
| 3 | orzdevinwang | 3707 |
| 4 | Radewoosh | 3627 |
| 5 | jqdai0815 | 3620 |
| 6 | Benq | 3564 |
| 7 | Kevin114514 | 3443 |
| 8 | ksun48 | 3434 |
| 9 | Rewinding | 3397 |
| 10 | Um_nik | 3396 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | cry | 167 |
| 2 | Um_nik | 163 |
| 3 | maomao90 | 162 |
| 3 | atcoder_official | 162 |
| 5 | adamant | 159 |
| 6 | -is-this-fft- | 158 |
| 7 | awoo | 155 |
| 8 | TheScrasse | 154 |
| 9 | Dominater069 | 153 |
| 10 | djm03178 | 152 |
It is well known* that you can insert somewhat arbitrary HTML into your CF blog or comment and Codeforces will happily render it, but it was only today that I learned you can do this in blog titles too!
I'm sure this is a perfectly sensible and reasonable feature that cannot be abused
One might even say it's a sus feature
... sorry, I'll leave.
mohagus
It seems there's some sort of filter, <script> and stuff don't work. But embeds do work:
lol it's funny how the image expands with the spoiler
It just is
My Blogs after this learning it..
Please don't show this to anyone :)
Preview:
Full:
Edit : nice feature and also it seems like when you try to write XSS script in js, it removes some dangerous codes while rendering it
InnerHTML has nothing to do with this.
There is definitely some sanitization going on, e.g. you can't use a
<script>tag. But it seems there was a conscious decision to allow most HTML, possibly they decided Markdown wasn't sufficient.