# Better theme settings on user front-end

**URL:** <https://meta.discourse.org/t/better-theme-settings-on-user-front-end/78477>\
**Category:** UX\
**Created:** [January 19, 2018, 2:12pm UTC](https://meta.discourse.org/t/better-theme-settings-on-user-front-end/78477 "2018-01-19T14:12:01Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)\
**Post date:** [January 19, 2018, 4:35pm UTC](https://meta.discourse.org/t/better-theme-settings-on-user-front-end/78477/3 "2018-01-19T16:35:06Z")

</div>

It shouldn’t have ruined anything except scaling for `<big>` and `<small>` tags, which should be avoided because they’re [obsolete specifications that can be removed at any moment](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/big). `<big>` specifically is very bad because it will nest and scale infinitely if defined with ems.

I can probably change the `<big>` definition to a rem unit to prevent the exploit and allow at least some scaling based on the root font-size, but it still should be considered as relevant as the `<blink>` tag.

---

_[View the full topic](https://meta.discourse.org/t/better-theme-settings-on-user-front-end/78477)._