# Tooltip popup for inline entity reference (e.g. for support pages) **URL:** \ **Category:** Ideas & Features\ **Created:** [August 26, 2023, 2:43pm UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019 "2023-08-26T14:43:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [August 26, 2023, 2:43pm UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019/1 "2023-08-26T14:43:15Z")
We often don’t want (users to) to navigate or open new panel, to prevent unnecessary distractions, whilst allowing additional information to be available from related entities. The most unintrusive solution has been known for long: tooltips, which popup by hovering over a tiny label such as a triangle in the corner of a field or inline reference. Here is a mockup, which shows the Support Page, which should not be necessary to display when there is a tooltip that shows the first x characters of the content. ![Tooltip for related page](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9bf4c5992e8afd4dd744dacc4f2ad2706cae2967.png) * * * Another way to implement this, is to have an ajax call inject the content under the inline entity link by expanding it, so that the rest of the content under it is pushed down. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [August 26, 2023, 6:38pm UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019/2 "2023-08-26T18:38:21Z")
This is a great idea 😀 How to define what content gets surfaced in the “preview” of an entity? Perhaps every DB can have a new option that defines which Field will contain the “preview” content for each entity. ---
**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\ **Post date:** [August 26, 2023, 7:08pm UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019/3 "2023-08-26T19:08:34Z")
Obsidian vibe ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 27, 2023, 7:47am UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019/4 "2023-08-27T07:47:54Z")
> [@Matt\_Blais](#): > > Perhaps every DB can have a new option that defines which Field will contain the “preview” content for each entity. It is already possible to choose which fields are shown when an entity is mentioned (click on the DB abbreviation icon of the mention). Unfortunately, rich text fields are not supported yet, but I can imagine that if they were, then the behaviour might well be similar to what’s proposed here. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [August 31, 2023, 4:54am UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019/5 "2023-08-31T04:54:07Z")
Awesome idea! ---
**Author:** ![Marloes](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/marloes/32/5926_2.png) [@Marloes](https://community.fibery.io/u/Marloes)\ **Post date:** [August 31, 2023, 7:01am UTC](https://community.fibery.io/t/tooltip-popup-for-inline-entity-reference-e-g-for-support-pages/5019/6 "2023-08-31T07:01:43Z")
Yes indeed!