You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All 6 "after" screenshots supplied with #3875 are tightly-cropped shots of only the raw weight-setters table (dimensions 1200x634 / 688x634 / 358x650 — notably not matching the stated 1280/768/mobile viewport widths used in the corresponding "before" shots, which are full-page captures including nav/header/breadcrumbs/tabs). The crop starts mid-page and excludes all surrounding chrome, so the PR's own evidence cannot confirm: whether the section reuses the panel's card/border conventions, correct spacing relative to the existing "VALIDATOR STAKE" bar chart and UID/HOTKEY table above it, or — most importantly at 358px mobile — whether the 4-column table (#, VALIDATOR, WEIGHT SETS, SHARE) overflows or needs horizontal scroll, since no viewport edges are visible in the mobile crop either.
Requirement
Confirm the weight-setters table renders within the mobile viewport without overflow, in the actual page context (not a cropped fragment).
What "done" looks like concretely: capture full-page (not cropped) screenshots at mobile (358-375px), tablet, and desktop, both themes, showing the table in its actual page context alongside the validator stake chart and UID/HOTKEY table above it. If the 4-column table overflows at mobile width, apply the same overflow-wrapper fix used elsewhere in the app (see the related ListShell/explorer table-overflow issues) rather than leaving it clipped.
Acceptance criteria
Full-page (uncropped) before/after screenshots exist at mobile, tablet, and desktop, both themes, matching the stated viewport dimensions
The weight-setters table's spacing/border/card treatment relative to its sibling sections is confirmed consistent
If mobile overflow is confirmed, it's fixed (horizontal scroll or mobile-card fallback) as part of this issue
If no overflow is found, this issue closes with the corrected full-page screenshots as evidence
Non-goals
Don't change the underlying weight-setters data or its ranking logic.
Size
Size: XS — keep this PR small (aim for ≤10 files / ≤1000 LOC).
Context
All 6 "after" screenshots supplied with #3875 are tightly-cropped shots of only the raw weight-setters table (dimensions 1200x634 / 688x634 / 358x650 — notably not matching the stated 1280/768/mobile viewport widths used in the corresponding "before" shots, which are full-page captures including nav/header/breadcrumbs/tabs). The crop starts mid-page and excludes all surrounding chrome, so the PR's own evidence cannot confirm: whether the section reuses the panel's card/border conventions, correct spacing relative to the existing "VALIDATOR STAKE" bar chart and UID/HOTKEY table above it, or — most importantly at 358px mobile — whether the 4-column table (#, VALIDATOR, WEIGHT SETS, SHARE) overflows or needs horizontal scroll, since no viewport edges are visible in the mobile crop either.
Requirement
Confirm the weight-setters table renders within the mobile viewport without overflow, in the actual page context (not a cropped fragment).
Deliverable
ListShell/explorer table-overflow issues) rather than leaving it clipped.Acceptance criteria
Non-goals
Size
Size: XS — keep this PR small (aim for ≤10 files / ≤1000 LOC).
Part of #2542.