# Problems with rich text object layout and lookup **URL:** \ **Category:** Bugs & Issues\ **Created:** [October 16, 2024, 4:12pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587 "2024-10-16T16:12:36Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [October 16, 2024, 4:12pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/1 "2024-10-16T16:12:36Z")
Fibery allows the center and side spaces to be sized to achieve optimal visualization by arranging the various objects very rationally. All good except for one thing. Document objects do not maximize and same thing for lookup objects. Can you explain why? Because the result of this lack is an unattractive visualization (where I put the arrows should have extended the object): ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8cb5b9df4290f6954447b1668faa21a319f44a99.png) You should fix this defect. Have a good evening. ---
**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:** [October 16, 2024, 4:26pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/2 "2024-10-16T16:26:49Z")
> [@DiegoKamp](#): > > Can you explain why? Because very wide columns tend to be rather difficult/unpleasant to read. It’s the same reason newspapers don’t have the body text of an article span the whole width of the page. ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [October 16, 2024, 5:17pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/3 "2024-10-16T17:17:36Z")
Hi Chris. Ok for the rich text object, although it should be the user who decides the width, also because there is the possibility of dividing the body of the document into columns. What good is that function otherwise? Much more important is that you solve the problem of lookup objects. ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [October 16, 2024, 5:30pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/4 "2024-10-16T17:30:16Z")
There is also the problem of the width of the view description! ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5565e63687d46b3dec8e749f2d9c766121b545dd.png) ---
**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:** [October 16, 2024, 5:46pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/5 "2024-10-16T17:46:02Z")
> [@DiegoKamp](#): > > the problem of lookup objects Can you clarify what the problem is > [@DiegoKamp](#): > > the problem of the width of the view description! Yeah, that should probably be fixed ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [October 16, 2024, 6:28pm UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/6 "2024-10-16T18:28:43Z")
It cannot be enlarged like other objects. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/c4ed0d1a657ec89663c0f78329dc4a609bcd0220.png) ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [October 19, 2024, 8:51am UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/7 "2024-10-19T08:51:12Z")
> [@DiegoKamp](#): > > It cannot be enlarged like other objects. Were you able to verify the problem of the width of lookup objects? Because this width is fixed. So if I align all the other objects in the view, the lookup object always stays the same size. ![immagine](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/6d17e720d29e3f2dee8186c359be3ede383c8d26.png) ---
**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:** [October 19, 2024, 8:57am UTC](https://community.fibery.io/t/problems-with-rich-text-object-layout-and-lookup/7587/8 "2024-10-19T08:57:26Z")
At some point, we hope to make lookups/formulas that result in collections behave in the same way as relation views on the UI, which would mean the width would be adjustable.