# Mini (Inline) Onebox Support RFC

**URL:** <https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400>\
**Category:** Feature\
**Tags:** rfc\
**Created:** [18 Julho , 2017 18:51 UTC](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400 "2017-07-18T18:51:46Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [11 Agosto , 2017 20:49 UTC](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400/21 "2017-08-11T20:49:07Z")

</div>

Almost 2 weeks later I still feel that `enable inline onebox on all domains` is a far better default. People are using it here and enjoying it lots. The edge case of [https://www.cnn.com](https://www.cnn.com) is fixed. There is minor level of muttering about people that need to discover the `<` `>` trick but I don’t think this warrants not making it default.

Should I go ahead and make it default?

---

_[View the full topic](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400)._