UI overflow bug: “show N properties” selector exceeds container bounds in API Reference (Receive section)

[ammonl]

🐛 Bug Description

In this Mintlify-rendered API Reference page, the UI control labeled “show 3 properties” in the Receive section overflows its parent container. The selector extends beyond the bounding box of the section, causing visual misalignment and reduced readability.

This appears to be a layout / overflow issue in the component that renders expandable object properties.

⸻

📍 Affected Page
• URL: https://docs.interhuman.ai/api-reference/stream-analyze
• Section: Receive
• Component: Property selector dropdown (“show 3 properties”)

⸻

🔍 Steps to Reproduce
1. Navigate to https://docs.interhuman.ai/api-reference/stream-analyze
2. Scroll to the Receive section
3. Observe the right-aligned selector labeled “show 3 properties”
4. Note that the selector exceeds the visual bounds of its enclosing card/container -- this only occurs when the browser width is less than 546px or between 1280 and 1400px.

⸻

✅ Expected Behavior

The “show N properties” selector should be fully contained within the section’s bounding box and align consistently with other sections (e.g., Send or Bindings), without overflow or clipping.

⸻

❌ Actual Behavior

The selector visually overflows the container, extending past the right edge of the section. This breaks layout consistency and may cause issues on smaller viewports.

⸻

🖥 Environment
• Documentation framework: Mintlify 4.2.255
• Browser: 143.0.7499.170 (Official Build) (arm64)
• OS: macOS Version 26.1 (Build 25B78)
• Reproducibility: 100%

⸻

📸 Screenshot

⸻

🛠️ Additional Notes / Hypothesis

This may be related to:
• A missing max-width or overflow: hidden on the section container
• A flexbox or grid alignment issue when rendering expandable property controls
• Inconsistent styling between sections that include multiple expandable objects

Happy to help test a fix or provide additional diagnostics if needed.

⸻

Thanks for maintaining Mintlify — overall the API reference UX is excellent. This issue seems localized and hopefully straightforward to resolve.