# Allow width/size control on interactive UI-extension components for table cells **URL:** \ **Category:** Develop, Build & Integrate\ **Tags:** cms-development-tools\ **Created:** [August 14, 2026, 10:01am UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081 "2026-08-14T10:01:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![OllieS](https://avatars.discourse-cdn.com/v4/letter/o/e274bd/32.png) [@OllieS](https://community.hubspot.com/u/OllieS)\ **Post date:** [August 14, 2026, 10:01am UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/1 "2026-08-14T10:01:00Z")
When building a CRM card with UI extensions, the interactive input components — `Input`, `NumberInput`, `Select` — render at a fixed, small size that can’t be changed. There’s no `width`, `size`, or `fullWidth` prop, and the documented `Box flex` fill mechanism has no effect on them inside a `Table` cell. So a `NumberInput` or `Input` placed in a table column stays a tiny box no matter how wide the column is set (via `width={n}` on the cell). **Use case** We have a lot of custom-logic & function requirements for building quotes that the native “Configure line items” screen doesn’t deliver on\*, so we’ve created a custom line-item card that mimics HubSpot’s native “Configure line items” screen — an editable grid of products with Qty, Unit price, Discount, part numbers, etc. The natural design is an editable table: one row per line, inputs in each column. But because the inputs can’t be widened to fill their columns, the grid is unusable for editing — every field is a cramped ~30px box regardless of the column width. Our only workaround is to make the whole table read-only and push all editing into a separate side panel, one line at a time, which is a big step back from a spreadsheet-style editor. **What we’d like** A supported way to control the rendered width (and ideally height/font size) of interactive input components — even a constrained set of options would be enough. For example: - a `width` / `size` prop on `Input` / `NumberInput` / `Select`, or - having these controls honour `Box flex` / fill their container the way read-only cells do, or - a documented “fill cell” behaviour for inputs placed inside `TableCell`. We understand the goal of keeping the CRM visually consistent, so this doesn’t need to be arbitrary CSS — just enough control to build a usable editable grid within HubSpot’s own design system. **Impact** This is the single blocker preventing UI-extension cards from replicating the editable line-item / table experiences that HubSpot ships natively. Any app trying to build an in-grid editor hits the same wall. \* specifically: - Can’t handle cost price being a different currency to unit price - Can’t handle bundles (yes there’re 3rd party add-ons, but they still don’t solve the bigger picture) - Some of our products require us to get a quotation from the supplier case-by-case, so need to flag where that’s the case - Handling cloning/moving/deleting multiple lines at once - Handling \>1 SKU per product that can all be searched against - More advanced searching logic & flagging (if SKU xxx.xxx.xxx is searched, it shows xxx.xxx.xxx and xxx.xxx.xxx.1, etc. with no flag to highlight this isn’t an exact match) - Handling inflationary price increases for multi-year contracts (in custom cards, we can teach logic to say SKU X denotes the start of a new year, and what % uplift to apply per year) that applies to both price and cost - Being able to change the FX rate to look at how margins would be affected if the GBP-EUR rate changed given we buy from suppliers in EUR and sell to customers in GBP, etc. ---
**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\ **Post date:** [August 14, 2026, 10:58am UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/3 "2026-08-14T10:58:36Z")
Hi @OllieS and Happy Friday! Great to see you on the HubSpot Community! Thank you so much for taking the time to detail your use case regarding the current limitations with [input sizing](https://developers.hubspot.com/docs/apps/developer-platform/add-features/ui-extensions/ui-components/standard-components/input) in CRM card UI extensions. I’d love to make sure our product teams see this feedback. For that, could you please submit the [HubSpot Developer Feedback form](https://developers.hubspot.com/feedback)? If it’s easier I can submit it on your behalf, just let me know. In the meantime, I’d love to check with our Top Experts: Hi @Anton, @SteveHTM and @zach_threadint, if you’ve discovered any partial workarounds beyond side-panel editing, I’m sure others in the Community would be interested as well. Thanks so much and have a wonderful weekend! Bérangère _- Please note that I’m out of the office until August 27th -_ ---
**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\ **Post date:** [August 14, 2026, 1:50pm UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/4 "2026-08-14T13:50:28Z")
Split this topic on August 14, 2026, 1:50pm UTC A post was merged into an existing topic: [Archived Content Rule Breakers Single Posts](https://community.hubspot.com/t/archived-content-rule-breakers-single-posts/153106/69) ---
**Author:** ![OllieS](https://avatars.discourse-cdn.com/v4/letter/o/e274bd/32.png) [@OllieS](https://community.hubspot.com/u/OllieS)\ **Post date:** [August 14, 2026, 1:58pm UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/5 "2026-08-14T13:58:42Z")
Submitted a form! ---
**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\ **Post date:** [August 14, 2026, 3:16pm UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/6 "2026-08-14T15:16:30Z")
Thanks so much @OllieS for submitting your valuable feedback via the form, we really appreciate it! And please let us know if you have any additional questions, we are here for you! 🧡 Bérangère _- Please note that I’m out of the office until August 27th -_ ---
**Author:** ![Connected-CRM-Studio](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/connected-crm-studio/32/226815_2.png) [@Connected-CRM-Studio](https://community.hubspot.com/u/Connected-CRM-Studio)\ **Post date:** [August 17, 2026, 4:30am UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/8 "2026-08-17T04:30:28Z")
Hi, @OllieS can confirm this matches the current state of UI Extension input components — the documented CRM action/UI component props don’t include a width, size, or fullWidth control for Input, NumberInput, or Select, and the fixed-size rendering inside table cells is a known constraint of the component library, not something you’re missing in the docs. [HubSpot](https://developers.hubspot.com/docs/apps/developer-platform/add-features/ui-extensions/ui-components/crm-action-components/overview) A few workarounds that other builders have used for editable-grid-style cards, none of which are as clean as native prop support but may help in the short term: - **Abbreviate cell content, expand on focus/interaction** : instead of trying to widen the persistent input, show a compact read-only value in the cell and open a small inline popover/modal (anchored to that cell) with a properly-sized input when the rep clicks it. More clicks than a true spreadsheet, but keeps the grid dense and avoids the cramped 30px box while editing. - **Move away from `Table` for the editable rows** : build your own row layout using `Box flex` containers stacked vertically instead of `Table`/`TableCell` — flex containers do respect width/fill in most UI Extension layouts, and the fixed-size behavior seems specific to inputs rendered inside actual `Table` cells. You lose native table styling (borders, header alignment) but regain control over input width. - **Batch-edit side panel with multi-select** : since you already have a read-only table + side panel fallback, you could extend the side panel to accept multiple selected rows at once (checkbox column in the table) so at least bulk edits like clone/move/delete/uplift % don’t require one-line-at-a-time — partially addresses your “handling multiple lines at once” pain point without solving the core width issue. For the actual ask — a supported width/size prop on interactive components — this is a genuine product gap in the UI Extensions component library, not a config issue on your end. I’d strongly recommend posting this on **HubSpot Ideas** (not just Developer Support) with the same detail you’ve given here, especially the “any app trying to build an in-grid editor hits the same wall” framing — that’s the kind of platform-level limitation that gets traction when other devs building similar line-item/quote tools upvote it. Worth linking this thread in the Ideas post so the context isn’t lost. ---
**Author:** ![OllieS](https://avatars.discourse-cdn.com/v4/letter/o/e274bd/32.png) [@OllieS](https://community.hubspot.com/u/OllieS)\ **Post date:** [August 17, 2026, 7:21am UTC](https://community.hubspot.com/t/allow-width-size-control-on-interactive-ui-extension-components-for-table-cells/156081/9 "2026-08-17T07:21:16Z")
Thanks for confirming. We’ve tried moving away from tables, but this then caused other limitations, so we’ve ultimately had to move to a stripped-back table with an editing panel. Have posted to ideas, so let’s hope this gets traction.