Skip to content

[scheduler] Remove dead CSS variable writes in EventTimelinePremiumContent#22720

Merged
brijeshb42 merged 5 commits into
mui:masterfrom
rita-codes:remove-events-scroll-left-leftover
Jun 10, 2026
Merged

[scheduler] Remove dead CSS variable writes in EventTimelinePremiumContent#22720
brijeshb42 merged 5 commits into
mui:masterfrom
rita-codes:remove-events-scroll-left-leftover

Conversation

@rita-codes

@rita-codes rita-codes commented Jun 9, 2026

Copy link
Copy Markdown
Member

Summary

Two dead CSS custom-property writes in EventTimelinePremiumContent, both no longer read anywhere on master:

  1. --events-scroll-left — the setter and the left: consumer were removed in earlier work. The only remaining references were two transform: translateX(calc(-1 * var(--events-scroll-left, 0) * 1px)) rules (EventsHeaderCellContent and EventsCell); with nothing setting the variable they always resolved to translateX(0). Confirmed as a leftover by @romgrk in [scheduler][timeline] Scrolling issues #22389 (comment).
  2. --has-scroll-y — written on the content root but never consumed (only --has-scroll-x is read, for the vertical size calc). The hasScrollY JS value is kept; it's still used for conditional rendering of the vertical scrollbar.

No behavior change — both writes were no-ops.

Context: #22389 (point 2).

The --events-scroll-left CSS variable is no longer written anywhere on
master (the setter and the left: consumer were removed earlier), so the
two `translateX(calc(-1 * var(--events-scroll-left, 0) * 1px))` rules in
EventTimelinePremiumContent always resolved to translateX(0). Drop them.

Confirmed as a leftover by @romgrk in mui#22389.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@rita-codes rita-codes self-assigned this Jun 9, 2026
@rita-codes rita-codes added type: enhancement It’s an improvement, but we can’t make up our mind whether it's a bug fix or a new feature. scope: scheduler Changes related to the scheduler. labels Jun 9, 2026
@rita-codes
rita-codes requested review from noraleonte and romgrk and removed request for noraleonte June 9, 2026 16:03
--has-scroll-y was written on the content root but never read anywhere
(only --has-scroll-x is consumed, for the vertical size calc). Drop the
dead write; the hasScrollY JS value is still used for conditional
rendering of the vertical scrollbar.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@rita-codes rita-codes changed the title [scheduler] Remove dead --events-scroll-left transforms [scheduler] Remove dead CSS variable writes in EventTimelinePremiumContent Jun 9, 2026
@rita-codes
rita-codes requested a review from noraleonte June 9, 2026 16:06
@code-infra-dashboard

code-infra-dashboard Bot commented Jun 9, 2026

Copy link
Copy Markdown

Deploy preview

https://deploy-preview-22720--material-ui-x.netlify.app/

Bundle size

Bundle Parsed size Gzip size
@mui/x-data-grid 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-pro 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-premium 0B(0.00%) 0B(0.00%)
@mui/x-charts 0B(0.00%) 0B(0.00%)
@mui/x-charts-pro 0B(0.00%) 0B(0.00%)
@mui/x-charts-premium 0B(0.00%) 0B(0.00%)
@mui/x-date-pickers 0B(0.00%) 0B(0.00%)
@mui/x-date-pickers-pro 0B(0.00%) 0B(0.00%)
@mui/x-tree-view 0B(0.00%) 0B(0.00%)
@mui/x-tree-view-pro 0B(0.00%) 0B(0.00%)
@mui/x-license 0B(0.00%) 0B(0.00%)

Details of bundle changes


Check out the code infra dashboard for more information about this PR.

@rita-codes
rita-codes enabled auto-merge (squash) June 10, 2026 09:06
@rita-codes
rita-codes disabled auto-merge June 10, 2026 09:31
@rita-codes rita-codes closed this Jun 10, 2026
@rita-codes rita-codes reopened this Jun 10, 2026
@brijeshb42
brijeshb42 merged commit 9718553 into mui:master Jun 10, 2026
21 checks passed
mbrookes pushed a commit to mbrookes/mui-x that referenced this pull request Jun 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: scheduler Changes related to the scheduler. type: enhancement It’s an improvement, but we can’t make up our mind whether it's a bug fix or a new feature.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants