Skip to content

Conversation

@BoDonkey
Copy link
Contributor

@BoDonkey BoDonkey commented Nov 5, 2025

Summary

Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
This PR fixes two issues. One, with the Apollo Astro starter kits, switching on breakpoint preview would cause all the fonts to use the base system font. This was due to how the :where() pseudoclass was wrapping elements and reducing their specificity to 0. Two, a user noted that responsive Tailwind classes were not working in breakpoint preview. This was due to how Tailwind 4.x nests media queries. Closes PRO-8513

What are the specific steps to test this change?

For example:

  1. Run the website and log in as an admin
  2. Open a piece manager modal and select several pieces
  3. Click the "Archive" button on the top left of the manager and confirm that it should proceed
  4. Check that all pieces have been archived properly
  1. Install Tailwind using npx astro add tailwind in a starter-kit-astro-apollo project.
  2. Add import "../styles/global.css" to the frontend/src/[...slug].astro file.
  3. To the frontend/src/templates/HomePage.astro add the following above the AposArea:
  <div class="p-4 sm:p-8 md:p-12 lg:p-16 m-2 sm:m-4 md:m-6 lg:m-8 bg-red-100 sm:bg-blue-100 md:bg-green-100 lg:bg-purple-100 text-base sm:text-lg md:text-3xl lg:text-6xl">
  Test content - watch me change!
</div>
  1. Symlink this branch into the frontend project.
  2. Observe that the styles have the same changes whether resizing the browser window or selecting different breakpoint sizes.
  3. Observe that the base fonts, like the navigation, do not change.
  4. Run the tests in this branch and see that they all pass.

What kind of change does this PR introduce?

(Check at least one)

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Build-related changes
  • Other

Make sure the PR fulfills these requirements:

  • It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
  • The changelog is updated
  • Related documentation has been updated
  • Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

@BoDonkey BoDonkey requested a review from ValJed November 5, 2025 19:27
@linear
Copy link

linear bot commented Nov 5, 2025

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.

2 participants