4 ms·
An open entry field for custom CSS would be a clunky but still welcome solution to this problem. It would also be extremely low-risk and low-effort on the maint
by _bxg1 6y ago
An open entry field for custom CSS would be a clunky but still welcome solution to this problem. It would also be extremely low-risk and low-effort on the maintainers' parts.
- dang 6y agoI wanted to do that but was told that Reddit encountered security issues with this, and so moved away from it in favor of a complex widget UI, which would not be a good fit for HN.
- andrewxdiamond 6y agoReddit had issues because user defined CSS was download and ran to other user's devices. In this case, you would only be able to affect your own version of the site, so any attack vector is mitigated
- dang 6y agoThat's a really good point.
- andrewflnr 6y agoI was thinking literally a handful of text fields validated against /[a-f0-9]{6}/. But yeah, maybe not quite as trivial as we would like.