Skip to content

DataViews: Always show primary action for list layout if hover isn't supported #69876

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

Merged
merged 1 commit into from
Apr 10, 2025

Conversation

yogeshbhutkar
Copy link
Contributor

@yogeshbhutkar yogeshbhutkar commented Apr 10, 2025

What?

Follow up to #69846
Related #69846 (review)

This PR ensures the primary action button is shown by default on screens that do not support the hover media query.

Why?

  1. To make it consistent with the table layout.
  2. To make the Primary Action Button accessible on devices that do not support hover media query.

How?

The corresponding visibility styles were added within the @media (hover: none) query.

Testing Instructions

  1. Navigate to Appearance -> Editor -> Pages.
  2. Make sure that the data is displayed in List Layout.
  3. Confirm that in Mobile Layout, the Primary Action, i.e., Edit is appropriately displayed.

Testing Instructions for Keyboard

Same.

Screenshots

Before After
before after

@yogeshbhutkar yogeshbhutkar marked this pull request as ready for review April 10, 2025 10:00
Copy link

github-actions bot commented Apr 10, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: yogeshbhutkar <yogeshbhutkar@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@yogeshbhutkar
Copy link
Contributor Author

Hi @t-hamano,

Following up on our previous discussions, I've created a follow-up PR here. Could you please have a look when you get a moment?
Thanks!

@yogeshbhutkar yogeshbhutkar force-pushed the fix/dataviews-list-layout branch from 2c4ef46 to 61b6f16 Compare April 10, 2025 10:30
Copy link
Contributor

@t-hamano t-hamano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for the follow-up.

@t-hamano t-hamano added [Type] Enhancement A suggestion for improvement. [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Package] DataViews /packages/dataviews props-bot Adding this label triggers the Props Bot workflow for a PR. labels Apr 10, 2025
@github-actions github-actions bot removed the props-bot Adding this label triggers the Props Bot workflow for a PR. label Apr 10, 2025
@t-hamano t-hamano merged commit 10ae0d7 into WordPress:trunk Apr 10, 2025
69 checks passed
@github-actions github-actions bot added this to the Gutenberg 20.7 milestone Apr 10, 2025
chriszarate pushed a commit to chriszarate/gutenberg that referenced this pull request Jul 1, 2025
…supported (WordPress#69876)

Co-authored-by: yogeshbhutkar <yogeshbhutkar@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Package] DataViews /packages/dataviews [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants