Limit ticket: sticky PLACE LIMIT footer overlaps/bleeds through form content until scrolled to bottom #500

Closed
opened 2026-07-18 15:32:29 +00:00 by leonardocolucci · 11 comments
leonardocolucci commented 2026-07-18 15:32:29 +00:00 (Migrated from gitlab.com)

Summary

The sticky PLACE LIMIT footer on the limit-order ticket overlaps and bleeds through the form content underneath it until the panel is scrolled to the bottom. Keeping the CTA pinned is clearly intentional and good — but the pinned state renders on top of live form controls with a semi-transparent background, so it reads as a glitch and hides inputs.

Same class of bug as #482 (sticky header bleed), different element.

Observed (desktop Chrome, EMBER/CORAL limit buy)

At scroll-top: the pinned PLACE LIMIT button covers the EXPIRY chips (NO EXPIRY / 24H / 7D are half-visible behind it) and the error banner ("Buy limits must be below the reference price.") sits directly on top of the dd/mm/yyyy date input, with both texts blending:

f001

Mid-scroll: the ADVANCED summary rows are readable through the button and banner — "MAKER FEE 0.040%" and the GAS row bleed through:

f004

Once fully scrolled, the footer settles into its natural in-flow position above MY OPEN LIMITS and everything looks correct — which is why this is easy to miss in QA.

Suggested fix

  1. Give the sticky footer an opaque (or blurred/backdrop-filter) background consistent with the glass theme, so content never shows through the CTA or the error banner.
  2. Add padding-bottom (≈ footer height) to the ticket's scroll container so the last controls (EXPIRY, date picker, ADVANCED) can scroll clear of the pinned footer instead of being covered by it.
  3. Consider keeping the validation error banner in normal document flow (or above the button inside the footer with the same opaque background) so it never obscures the input it refers to.
## Summary The sticky PLACE LIMIT footer on the limit-order ticket overlaps and bleeds through the form content underneath it until the panel is scrolled to the bottom. Keeping the CTA pinned is clearly intentional and good — but the pinned state renders on top of live form controls with a semi-transparent background, so it reads as a glitch and hides inputs. Same class of bug as #482 (sticky header bleed), different element. ## Observed (desktop Chrome, EMBER/CORAL limit buy) **At scroll-top:** the pinned PLACE LIMIT button covers the EXPIRY chips (NO EXPIRY / 24H / 7D are half-visible behind it) and the error banner ("Buy limits must be below the reference price.") sits directly on top of the `dd/mm/yyyy` date input, with both texts blending: ![f001](/uploads/8398407487e456f02150b2aa67e9c11f/f001.png) **Mid-scroll:** the ADVANCED summary rows are readable *through* the button and banner — "MAKER FEE 0.040%" and the GAS row bleed through: ![f004](/uploads/961363dab324d8b1c535349357737b17/f004.png) Once fully scrolled, the footer settles into its natural in-flow position above MY OPEN LIMITS and everything looks correct — which is why this is easy to miss in QA. ## Suggested fix 1. Give the sticky footer an opaque (or blurred/backdrop-filter) background consistent with the glass theme, so content never shows through the CTA or the error banner. 2. Add `padding-bottom` (≈ footer height) to the ticket's scroll container so the last controls (EXPIRY, date picker, ADVANCED) can scroll clear of the pinned footer instead of being covered by it. 3. Consider keeping the validation error banner in normal document flow (or above the button inside the footer with the same opaque background) so it never obscures the input it refers to.
PlasticDigits commented 2026-07-25 04:14:13 +00:00 (Migrated from gitlab.com)

Validation banner should be in normal document flow.

Validation banner should be in normal document flow.
PlasticDigits commented 2026-07-25 04:33:08 +00:00 (Migrated from gitlab.com)

mentioned in commit 7b4f786a7c

mentioned in commit 7b4f786a7c6a34feb10c688cff55f33bcc4969ac
PlasticDigits commented 2026-07-25 04:33:37 +00:00 (Migrated from gitlab.com)

mentioned in merge request !1034

mentioned in merge request !1034
PlasticDigits commented 2026-07-25 04:38:04 +00:00 (Migrated from gitlab.com)

mentioned in commit a8c0755cd9

mentioned in commit a8c0755cd97d84e05c99f305195f91f6497ec333
PlasticDigits commented 2026-07-25 04:49:03 +00:00 (Migrated from gitlab.com)

mentioned in commit 0be38dc852

mentioned in commit 0be38dc852561f1b0ec2b6ce6f798f6edceb0b6c
PlasticDigits commented 2026-07-25 04:49:33 +00:00 (Migrated from gitlab.com)

mentioned in commit 3a0069ce89

mentioned in commit 3a0069ce89de94c5e340d9e652d2e4cc018d4aef
PlasticDigits (Migrated from gitlab.com) closed this issue 2026-07-25 04:49:33 +00:00
PlasticDigits commented 2026-08-15 13:18:35 +00:00 (Migrated from gitlab.com)

mentioned in issue #527

mentioned in issue #527
PlasticDigits commented 2026-08-15 13:18:35 +00:00 (Migrated from gitlab.com)

marked as related to #527

marked as related to #527
PlasticDigits commented 2026-08-16 08:14:36 +00:00 (Migrated from gitlab.com)

mentioned in merge request !1062

mentioned in merge request !1062
leonardocolucci commented 2026-08-17 21:14:16 +00:00 (Migrated from gitlab.com)

Thanks for the fast fix (!1034) and for moving the validation banner into normal flow — the ticket footer reads cleanly now.

Thanks for the fast fix (!1034) and for moving the validation banner into normal flow — the ticket footer reads cleanly now.
PlasticDigits commented 2026-08-18 12:08:53 +00:00 (Migrated from gitlab.com)

mentioned in issue #561

mentioned in issue #561
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
code/cl8y-dex-terraclassic#500
No description provided.