Skip to content

fix(ADBLABS-188): hide article top actions across mobile and tablet - #129

Open
luisSilvaEs wants to merge 1 commit into
mainfrom
feat/mobile-content-order
Open

luisSilvaEs wants to merge 1 commit into
mainfrom
feat/mobile-content-order

Conversation

@luisSilvaEs

Copy link
Copy Markdown
Collaborator

Summary of changes

  • Hide the top article-meta actions (Copy link, Download, Feedback) at tablet widths (768–1023px), per acceptance criteria
  • Fix the existing mobile hide rule, which only covered widths ≤375px, so it now covers the full mobile range (common phone widths like 393px were previously still showing the row)

Relevant Links

Test URLs:

Checklist

  • This PR has visual changes, and has been reviewed by a designer.
  • This PR has code changes, and our linters still pass.
  • This PR affects production code, so it was browser tested (see below).

Validation

  1. Make sure all PR checks have passed.
  2. Pull down the branch and run locally or view on the PR testing link.
  3. Verify the implementation against the design and story requirements.

Validation steps

  • Copy link / Download / Feedback actions at the top of the article are hidden at tablet widths (768–1023px)
  • Copy link / Download / Feedback actions at the top of the article are hidden at mobile widths, including common widths like 375px and 393px (not just the previous ≤375px-only breakpoint)
  • Copy link / Download / Feedback actions at the top of the article remain visible at desktop widths (≥1024px)
  • Bottom article-meta actions (end of article) are unaffected by this change

Browser Testing

We should aim to support the latest version of the listed browsers. For older versions or other browsers not on the list, content should be accessible, even if it doesn't completely match the designs.

Developers should test as they work in the browsers available on their machines. If they have access to other devices to test other browser/OS combinations, they should do that when possible.

Blocks and pages should undergo comprehensive testing to ensure they work as expected in real-use scenarios. Standard testing during pre-production should include at least these browsers.

  • Firefox
  • Chrome
  • Safari

Dark mode and light mode

Most pages support both dark and light mode, based on prefers-color-scheme.
Changes that affect the frontend should support both color schemes.

  • Frontend changes have been tested in both light mode and dark mode.

@aem-code-sync

aem-code-sync Bot commented Oct 2, 2026

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run all PSI checks
  • Re-run failed PSI checks
  • Re-sync branch
Commits

@aem-code-sync

aem-code-sync Bot commented Oct 2, 2026

Copy link
Copy Markdown

This branch was successfully deployed

1 active deployment
feat/mobile-content-order — 7fde1065 Deployed Oct 2, 2026 by aem-code-sync[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant