-
Notifications
You must be signed in to change notification settings - Fork 897
Premium Analytics: keep dialog focus rings from being clipped #52110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Significance: patch | ||
| Type: fixed | ||
|
|
||
| Dialogs: keep the comment field's focus ring from being clipped by the dialog footer. | ||
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| // Pinned chrome zeroes the scroll container's block padding on that edge, | ||
| // clipping a focus ring, which sits twice the focus width outside its control. | ||
| // Drop when @wordpress/ui ships https://github.com/WordPress/gutenberg/pull/82443. | ||
| header ~ [data-wp-ui-overlay-scroll-container] { | ||
| padding-block-start: calc(var(--wpds-border-width-focus) * 2); | ||
| } | ||
|
|
||
| [data-wp-ui-overlay-scroll-container]:has(~ footer) { | ||
| padding-block-end: calc(var(--wpds-border-width-focus) * 2); | ||
| } | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Upstream (WordPress/gutenberg#82443) also subtracts the same clearance from the adjacent chrome padding, so the header-to-content and content-to-footer gaps stay unchanged. This shim only does the first half, so each pinned edge is currently 3px taller than trunk, and it will shrink back by that much when the Mirroring the other half makes the bump a pure no-op: header:has(~ [data-wp-ui-overlay-scroll-container]) {
padding-block-end: calc(var(--wpds-dimension-gap-lg) - 1px - var(--wpds-border-width-focus) * 2);
}
[data-wp-ui-overlay-scroll-container] ~ footer {
padding-block-start: calc(var(--wpds-dimension-gap-lg) - 1px - var(--wpds-border-width-focus) * 2);
}The
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch, applied. I hadn't spotted that upstream trims the chrome side too, so the gaps were 3px wider than trunk. Mirroring both halves means the |
||
|
|
||
| // The chrome gives that clearance back, so the gap matches trunk. `- 1px` is | ||
| // the separator slot; an unlayered rule cannot read the layered value. | ||
| header:has(~ [data-wp-ui-overlay-scroll-container]) { | ||
| padding-block-end: calc(var(--wpds-dimension-gap-lg) - 1px - var(--wpds-border-width-focus) * 2); | ||
| } | ||
|
|
||
| [data-wp-ui-overlay-scroll-container] ~ footer { | ||
| padding-block-start: calc(var(--wpds-dimension-gap-lg) - 1px - var(--wpds-border-width-focus) * 2); | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Significance: patch | ||
| Type: bugfix | ||
|
|
||
| Premium Analytics: keep the dialog focus ring from being clipped by the dialog footer. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Significance: patch | ||
| Type: fixed | ||
|
|
||
| Dialogs: keep the focus ring from being clipped by the dialog footer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a user-visible fix, so it should also get entries in the plugins that render the dashboard, matching what #52060, #51882 and #51772 did (
plugins/jetpackandplugins/premium-analytics, plusplugins/wpcomshin #51772). Otherwise it only reaches the package changelog. For example:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, the last few PA UI PRs all added those two. Added entries for
plugins/jetpackandplugins/premium-analytics. Leftwpcomshout to match 52044 and 51873, happy to add it if you think Atomic users should see it.